Re: which log to diagnose crash

1998-08-29 Thread Richard E. Hawkins Esq.
marcus wrote, > > It didn't sync the disks, so we got to wait while it e2fsck'd a pair of > > 4G drives (*sigh* at least the third disk had been disconnected. I > > need to poke around and figure out how to get it to do the two scsi > > drives simultaneously . . .). > Syncing the disks is no

Re: which log to diagnose crash

1998-08-29 Thread Marcus Brinkmann
On Fri, Aug 28, 1998 at 11:15:30AM -0500, Richard E. Hawkins Esq. wrote: > > It didn't sync the disks, so we got to wait while it e2fsck'd a pair of > 4G drives (*sigh* at least the third disk had been disconnected. I > need to poke around and figure out how to get it to do the two scsi > dri

Re: which log to diagnose crash

1998-08-28 Thread Richard E. Hawkins Esq.
> When X freezes, there's no a priori reason why anything should be logged. > The rest of the machine should be running normally, and the best course > of action is to telnet in through the network or a serial line and kill > the X session (using startx it'll be an xinit process). This wasn't an

Re: which log to diagnose crash

1998-08-28 Thread David Wright
On Thu, 27 Aug 1998, Richard E. Hawkins Esq. wrote: > my bosses machine crashed this mornging, leaving his Xsession frozen, > and no kernel panic message. > > Which log do I look in for this, or does a kernel panic get logged? > how do i figure out what happened? When X freezes, there's no a

which log to diagnose crash

1998-08-27 Thread Richard E. Hawkins Esq.
my bosses machine crashed this mornging, leaving his Xsession frozen, and no kernel panic message. Which log do I look in for this, or does a kernel panic get logged? how do i figure out what happened? rick -- These opinions will not be those of ISU until it pays my retainer.