WD describes how to reduce the output from syslogd, but Synology (at least my DS210j w/ DSM2.3)
uses the 'busybox' implementation for syslogd, which has different (reduced) configuration options,
and besides, it ignores the /etc/syslog.conf (used in 'standard' Linux/Unix and described in WD note):
- Code: Select all
System logging utility. Note that this version of syslogd ignores /etc/syslog.conf.
-n Run in foreground
-O FILE Log to given file (default:/var/log/messages)
-l n Set local log level
-S Smaller logging output
-s SIZE Max size (KB) before rotate (default:200KB, 0=off)
-b NUM Number of rotated logs to keep (default:1, max=99, 0=purge)
-R HOST[:PORT] Log to IP or hostname on PORT (default PORT=514/UDP)
-L Log locally and via network (default is network only if -R)
-D Drop duplicates
-C[size(KiB)] Log to shared mem buffer (read it using logread)
I can see that by default on my NAS the -S option is activated.
In any case, the amount of data that the NAS writes from syslog is quite small, so IMHO that is not
a primary source for keeping the disk awake.
Synology can probably improve things a little bit by 'tuning' several custom/proprietary processes
(like scemd, or a few whose name is syno<something>) but I doubt it would completely solve the issue,
as other users processes will be running.
Maybe a solution could be to move to an architecture with solid-state memory for the system,
user commands, logs, extra packages, etc. and dedicate the conventional harddisk uniquely to store user's data.