On Sun, 10 Jun 2007 08:32:20 -0500, Mike Chambers wrote: > On Sun, 2007-06-10 at 12:58 +0000, Beartooth wrote: > >> Actually, no, I don't even know what logs to look in, not where to find >> them. Is there a standard place to look? > > /var/log > > And using the "uptime" command, you can see how long it's been since > your machine actually rebooted. Now there are three of them definitely doing it! Two more did it this morning while I sat here. /var/log in two of them includes boot.log, boot.log.1, as well as .2,.3, and .4; the other (which I was sure of yesterday) has only boot.log. The fourth, an old P2 which has so far *not* been having the problem, has boot.log and boot.log.1 Are those the logs I want to look in? And for what? uptime for the three with problems lists times of around an hour; for the old P2, it says 6 1/2 days. Dunno if this is relevant. I make a habit, whenever I think of it (probably two or three times a week; oftener when I've just installed a brand-new release), of running a sequence of commands consisting of "yum clean all" followed by "rpm --rebuilddb," then "updatedb," and finally "yum update." The strangest thing is that my main machine, which pulled the trick this morning, is still running FC6. We have had a few short (like under 10-second) power glitches here lately; but all the machines are on UPSs, which barely managed to beep once. What's more, the main machine, which rebooted spontaneously for the first time this morning, is on the same UPS as the old P2, which did not. One of these UPSs (an APC Back-UPS RS 1500) is only a month or two old. Another (an APC Back-UPS 650) has some age on the battery, but has shown no more sign of unhappiness than the others. The third (an APC Back-UPS Pro 650) has some age on its present second battery, but has also not complained. -- Beartooth Staffwright, PhD, Neo-Redneck Linux Convert Remember I know precious little of what I am talking about.
