Synergyc spamming messages.log

Question

Just wanted to let you guy's know that if you follow the instructions on the archwiki for autostarting the synergy client using the /etc/rc.d/synergyc file, then you may want to edit the line that calls synergy to include "-d WARNING". This way only messages with level "WARNING" and above get added to messages.log.
Example spam messages:
May 26 22:30:46 localhost Synergy 1.4.6: 2012-05-26T22:30:46 INFO: entering screen
        /build/src/synergy-1.4.6-Source/src/lib/synergy/CScreen.cpp,103
May 26 22:30:47 localhost Synergy 1.4.6: 2012-05-26T22:30:47 INFO: leaving screen
        /build/src/synergy-1.4.6-Source/src/lib/synergy/CScreen.cpp,121
Example /etc/rc.d/synergyc
#!/bin/bash
. /etc/rc.conf
. /etc/rc.d/functions
#Put the server host name in the following line
SERVERALIAS="server-host-name"
PID=`pidof -o %PPID /usr/bin/synergyc`
case "$1" in
start)
stat_busy "Starting Synergy Client"
[ -z "$PID" ] && /usr/bin/synergyc -d WARNING "$SERVERALIAS"
if [ $? -gt 0 ]; then
stat_fail
else
/usr/bin/xset r on
add_daemon synergyc
stat_done
fi
stop)
stat_busy "Stopping Synergy Client"
[ ! -z "$PID" ] && kill -9 $PID
if [ $? -gt 0 ]; then
stat_fail
else
rm_daemon synergyc
stat_done
fi
restart)
$0 stop
sleep 1
$0 start
echo "usage: $0 {start|stop|restart}"
esac
exit 0
This is useful so that your messages.log isn't full of unimportant stuff if you're trying to debug other problems, also reduces the overall number of reads and writes which may be good for people running on SSDs (though the var directory should probably be put on a different HDD if possible in that case).

Answer 1

Awesome, I just did that.
https://wiki.archlinux.org/index.php/Sy … leshooting