Syslogd mark interval
Forum: DSL Ideas and Suggestions
Topic: Syslogd mark interval
started by: chaostic
Posted by chaostic on June 23 2008,13:59First, is /etc/init.d/sysklogd used to start syslog if it is added to the boot line?
If so, I think the mark interval should be changed. Currently, the busybox syslogd mark's the log every 20 minutes. It's excessive. The bb syslogd does respond to the -m [n] option, where [n] is a number in minutes.
I think /etc/init.d/sysklogd, if used, should be changed to include that option for either 180 minutes (3 hours) or 1440 minutes (24 hours).
Also, /etc/syslog.conf is unneeded since the full syslogd is not used. BB syslogd ignores it. It could be erased.
Edit: Or you could simply add -m 0, to turn off interval marking at all.
Posted by mikshaw on June 23 2008,18:25
20 minutes may be a little excessive, but I think 3 hours is excessively infrequent. I'm not sure what the original intent of mark was, but personally I use it to quickly get a visual of how much time has passed between events. I couldn't see it being very useful with an interval of more than an hour. 24 hours is completely pointless, from my point of view, considering I shut the thing down every night.
Posted by chaostic on June 23 2008,18:51
I tend to leave mine on for days/weeks on end (Thinclient, using 15w powersupply, as my streaming radio player, server, recorder, and torrent station ). Since bb syslogd rotates based on size instead of days, (I'm actually used to weekly rotated logs on OSX), the 24h mark provides a nice difference between days. Since syslogd also uses the extended (Normal) output instead of the short (with option -s) output, the full date and time are already on the events to provide that visual, imho.
I was just thinking in more of a "space/memory saving" fashion/use to go along with the whole "dsl" mentality :P
Oh, and thanks for letting me know where bootcodes are normally launched from. Useful for a remaster.