[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: syslogd regular marks on Debian




On Mon, 5 Nov 2001, Rymland, Boaz (Boaz) wrote:

> shachar shemesh wrote:
>
> > A. Know that the reason no logs were seen was because nothing
> happened,
> > and not, say, because syslogd could not write to the logs
> > B. Test your APM settings, by spinning your HD back up just as it was
> > spinning down due to no-use.
> > C. If your system reboots unexpectedly - know when that happened
> > (approximatly).
> > D. Justify buying a bigger HD.
> > E. Making sure there WILL be prolems when you root partition gets full
>
> > (not that I log to my root partition, but....)
>
> I liked E best,but about C - Dah! Maybe you should simply look for that
> "syslogd 1.4.1 started..." and the following kernel messages at the same
> time (second plus/minus) instead?... .
> It's a bit more accurate to get the reboot time this way.

unless your machine got stuck - in which case, you won't know when that
happened. the reboot entries will then be when you came to the machine,
found it stuck, and hit the red button ;)

--
guy

"For world domination - press 1,
 or dial 0, and please hold, for the creator." -- nob o. dy


=================================================================
To unsubscribe, send mail to linux-il-request@linux.org.il with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail linux-il-request@linux.org.il