chaostic
Group: Members
Posts: 328
Joined: Mar. 2005 |
 |
Posted: June 23 2008,18:51 |
 |
| 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  ). 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.
|
.
DSL Market ,
Great VPS hosting provided by Tektonic
