On Tue, 2002-08-27 at 18:19, fred smith wrote: > On Tue, Aug 27, 2002 at 03:21:12PM -0400, [EMAIL PROTECTED] wrote: > > I need some help. > > > > 1. I have a server that has been up for 100+ days and I need to do some > > hard drive work on. I know that the server has an available 33 gig scsi > > drive on it, but I'm not sure how linux saw the drive. Unfortunately due > > to the amount of uptime, dmesg no longer shows the bootstrap sequence. Is > > there anyway to get linux to do something like a re-scan of the drives and > > report to me what it finds? Since this machine is in production, I can > > not bounce it without a lot of headache. > > less /var/log/dmesg > > appears to be the original boot log. it is NOT the same thing you see > (days or weeks later) when doing "dmesg | less".
good, no, great tip Fred. I had no idea. Now if I can just find out what a kernel ring buffer is :) I can't believe I never actually looked in there before. I have pissed and moaned and threatened to write a script that does a less +G /var/log/messages since I assumed that dmesg was a cat /var/log/dmesg. I have the boot messages for an internal server that was last booted lets see, [bhughes@compaq2 bhughes]$ uptime 9:22pm up 348 days, 6:53, 3 users, load average: 0.09, 0.06, 0.01 [bhughes@compaq2 bhughes]$ I had no Idea. Thanks again. I swear, every time I get to thinking that I am spending too much time reading this list I learn something from reading a thread that I had little interest in or help to offer. Bret -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
