DSL Ideas and Suggestions :: Syslogd mark interval



First, 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).

Line 11-14:
Code Sample

# Options for start/restart the daemons
# For remote UDP logging use SYSLOGD="-r"
#
SYSLOGD=""


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.

Quote (line 383 @ /etc/init.d/dsl-config,)
  if checkbootparam "syslog"; then
     /sbin/syslogd >/dev/null && echo " ${GREEN}syslog started.${NORMAL}"
  fi
syslogd is started directly when using the boot option.  It looks like sysklogd is a typical start/stop/restart script of the type used either when controlling it manually or using the traditional style of initializing daemons during boot.

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.

Quote (mikshaw @ June 23 2008,14:25)
Quote (line 383 @ /etc/init.d/dsl-config,)
  if checkbootparam "syslog"; then
     /sbin/syslogd >/dev/null && echo " ${GREEN}syslog started.${NORMAL}"
  fi
syslogd is started directly when using the boot option.  It looks like sysklogd is a typical start/stop/restart script of the type used either when controlling it manually or using the traditional style of initializing daemons during boot.

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.

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 :D ). 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.


original here.