dmesg on 2.6
2007-12-24 21:03:00
I have received a couple of replies that are useful in determining the last
time the system rebooted ("who -b" & "last reboot"), but I'm trying to match
up date & time to the system error messages generated by "dmesg" Note the
difference in the output example below from a Solaris8 system:
Oct 18 13:25:05 systema su: [ID 810491 auth.crit] 'su acollier' failed for
rdinwid on /dev/pts/10
Oct 18 13:33:47 systema last message repeated 1 time
Oct 18 13:42:15 systema su: [ID 810491 auth.crit] 'su acollie' failed for
rdinwid on /dev/pts/9
Oct 18 13:42:30 systema last message repeated 1 time
My original post:
On Solaris8, the dmesg command returns system information since the last
reboot and includes the date & time of the event. In Solaris 2.6, it
doesn't return the date & time, which I need for the problem I'm
researching. Can anyone point me in the right direction to gather this info
in a format at least similar to Solaris8?
/var/adm/messages has a gap in it for the time period I'm looking for, so
it's only an indicator of the problem.
This is the portion of dmesg output that I would like to get the date & time
for:
zs0 at sbus0: SBus0 slot 0xf offset 0x1100000 Onboard device sparc9 ipl 12
zs0 is /sbus at 1f,0/zs at f,1100000
zs1 at sbus0: SBus0 slot 0xf offset 0x1000000 Onboard device sparc9 ipl 12
zs1 is /sbus at 1f,0/zs at f,1000000
keyboard is </sbus at 1f,0/zs at f,1000000> major <29> minor <2>
mouse is </sbus at 1f,0/zs at f,1000000:b> major <29> minor <3>
stdin is </sbus at 1f,0/zs at f,1000000> major <29> minor <2>
cgsix0 at sbus0: SBus0 slot 0x3 offset 0x0 SBus level 5 sparc9 ipl 9
cgsix0 is /sbus at 1f,0/cgsix at 3,0
cgsix0: screen 1152x900, single buffered, 1M mappable, rev 11
stdout is </sbus at 1f,0/cgsix at 3,0> major <39> minor <0>
cpu 1 initialization complete - online
TIA
Ron
Comments
Got something to say?
You must be logged in to post a comment.
