Bug 988395

I have investigated the issue - here are my initial thoughts:

Basically I see two options:

a) just limit the debug output when starting synergy:

from "man synergyc" (or "man synergys"):

       -d, --debug <level>
              filter out log messages with priority below level.  level may be: FATAL, ERROR, WARNING, NOTE, INFO, DEBUG, DEBUGn
              (1-5).


b) or alternatively use a minimal patch and just change the default log level to NOTE

src/lib/synergy/CArgsBase.cpp:
[...]
m_logFilter("NOTE"),

I currently working on updating synergy to 1.4.12 and probably I'll add the "synergy" GUI to the package. If synergy is started via that program, it will use NOTE as default log level.

(In reply to Christian Krause from comment #1)
> I have investigated the issue - here are my initial thoughts:
> 
> Basically I see two options:
> 
> a) just limit the debug output when starting synergy:
> 
> from "man synergyc" (or "man synergys"):
> 
>        -d, --debug <level>
>               filter out log messages with priority below level.  level may
> be: FATAL, ERROR, WARNING, NOTE, INFO, DEBUG, DEBUGn
>               (1-5).
Understood... I am not setting *any* debug level but my /var/log/messages
file is being flood with what appear to be debug messages.
 
> 
> 
> b) or alternatively use a minimal patch and just change the default log
> level to NOTE
> 
> src/lib/synergy/CArgsBase.cpp:
> [...]
> m_logFilter("NOTE"),
> 
> I currently working on updating synergy to 1.4.12 and probably I'll add the
> "synergy" GUI to the package. If synergy is started via that program, it
> will use NOTE as default log level.
If doing that stops the filling up my log file needless log entries
then I'm find with that...  But I still have to question whether the 
NOTES I changed into DEBUG messages are really NOTES? They seem more
like DEBUG message than notes...

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.