--- sean <[EMAIL PROTECTED]> wrote: > could someone please explain the -systohc flag > passed > to hwclock in init.d/halt (i have mdk8,2 but i also > noticed this setting in 9.0rc3)? this has caused my
The idea is you set your system clock correctly (say with ntpd or something) while the system is running, but you probably don't (most people don't) use hwclock to set the hwclock (--systohc is the way to do it), so it sets it on shutdown, so next time you boot you'll have close to the right time. > laptop many problems in crash scenarios coming from > resuming and dieing with incorrect time, > CTRL-ALT-DEL > brings down sys and writes incorrect value to bios. We should figure out why. > i > have switched my setting to the -hctosys flag as > recommended in hwclock man page. No, that makes absolutely no sense. You're setting the system time as you shut it down. If you don't want the --systohc because it's causing problems, just comment it out. There's actually almost never a reason to use --hctosys. The manpage actually recommends you do that in *startup*, but you boot with the hardware time anyway. __________________________________________________ Do you Yahoo!? U2 on LAUNCH - Exclusive greatest hits videos http://launch.yahoo.com/u2
