another clock problem?
the clock on my indy often loses 20hrs between boots. it seems to always be
exactly 20hrs. i've tried setting the date at the boot command prompt and also
from the linux prompt. also it often forces a fsck erroneously reporting that
the file system hasnt been checked in over 180 (or so) days...
i havent done exhaustive tests to try and nail down the exact circumstances
this happens (this is a production box that really only gets turned on when i
need to use it) but i have a nagging feeling that it may be something to do
with the different shutdown methods. sometimes i use halt and sometimes i hit
the power button which appears to have the same effect.
tangent: is it possible to shutdown to the prom menu?
GREG
Reply to: