topic Re: dmesg vs syslog.log in Operating System - HP-UX

dmesg vs syslog.log

Michael R. Monteith — Wed, 15 Mar 2006 11:57:55 GMT

I had a discussion with another sa. I told him I had dmesg setup in cron to output to /var/adm/messages. He said that was redundant since that same information is in syslog.log. I disagreed with him but wondered if there was something explaining that at HP somewhere? I say that the information might be in dmesg and not syslog.log is why I do that.

Michael

Re: dmesg vs syslog.log

Pete Randall — Wed, 15 Mar 2006 12:02:51 GMT

A simple examination of the contents of the dmesg buffer versus the contents of the syslog file would make it pretty obvious that they were different.

A careful examination of the man pages would also point out the difference. Dmesg is dianostics, syslog can be most anything, depending on how it is configured - but it rarely contains any of the dmesg diagnostics.

Pete

Re: dmesg vs syslog.log

A. Clay Stephenson — Wed, 15 Mar 2006 12:09:01 GMT

Well, you are both wrong, kinda, sorta. First, dmesg is a circular buffer of fixed size so that once the buffer fills, only the most recent data are available but messages can be stored in this buffer before /var is even mounted. Secondly, syslog does as syslog is configured so that messages in syslog may or may not correspond to those in dmesg. Your approach has merit because those two logs are not always the same. You should be aware that regardless of the cron period, it is possible to fill the dmesg buffer so that data are lost between cron captures.

Re: dmesg vs syslog.log

Michael R. Monteith — Wed, 15 Mar 2006 12:15:12 GMT

Thanks to both of you. This is why I recommended putting in cron:
05,15,25,35,45,55 * * * * /usr/sbin/dmesg - >>/var/adm/messages 2>&1

As we used to do that to give you time and dates when entries are put in and also a running record. Works nicely.

Michael

Re: dmesg vs syslog.log

DCE — Wed, 15 Mar 2006 12:36:30 GMT

Michael,

As Clay stated, dmesg is a fixed length rolling buffer. I have seen it fill up and roll over in less than 10 minutes. I would rely on your cron job to capture all of the output of dmesg.

If you really want the dmesg output you could try runnong a tail -f > /var/adm/some_sile_name against it in the background

Re: dmesg vs syslog.log

Kent Ostby — Wed, 15 Mar 2006 13:03:52 GMT

There is some overlap here and syslog.log is nice because it gets timestamped.

You may want to consider a way to timestamp the dmesg output that you are sending to /var/adm/messages or adding an echo command that puts the time in there as well.

Re: dmesg vs syslog.log

Michael R. Monteith — Wed, 15 Mar 2006 13:16:08 GMT

Using the cron entry above does that. You get date/time stamp. That at least confirms when an entry made it into dmesg. I know I've seen entries before using that method and wondered if it was new or old. The cron entry method at least does that.

Michael