Bugger sent to a person and not the group => I think it was "wolfi" and "Anders" (may be more?) who solved it => => I had to try it a couple of times before it worked OK. => => below a reply from wolfi => ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ => => Hi all, => => I now managed to shut down the box and reboot it without getting the => time settings messed up. => What I did: => After Anders suggested, that my /etc/adjtime file might be faulty, I => renamed it to /etc/adjtime.old to disable it. => Then I went into YaST2, timezone settings, changed something, changed it => back, just to make sure YaST2 will write the data which I basically only => wanted to make sure it will be 'kept'. => => The new /etc/adjtime looks as follows: => => 0.000000 0 0.000000 => 0 => UTC => => Thanks to Anders & Cheers .... Wolfi => ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ => mine came out as => 0.000000 1038853285 0.000000 => 1038853285 => LOCAL => => were the old copy was => 11187.809267 1038803068 0.000000 => 1038803068 => LOCAL => ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ => => => Just to refresh your memory on Saturday 07 December 2002 00:59 New Zealand => time, Carlos E. R. told us: => => => The 02.12.01 at 22:32, wolfi wrote: => => => => => => > Did you find a solution for this? => => > I have got exactly the same problem on one of my boxen. => => > In /etc/init.d/boot.clock it says -> see below. => => > => => > This one seems to be important: => => > /sbin/hwclock --hctosys $HWCLOCK => => > which means, that on boot system time is adjusted to BIOS time. But in => => > fact, the opposite happens. => => => => It sets system clock from CMOS (BIOS) time. Look the manual page: => => => => --hctosys => => Set the System Time from the Hardware Clock. => => => => Also set the kernel's timezone value to the local timezone as => => indicated by the TZ environment variable and/or /usr/share/zoneinfo, as => => tzset(3) would interpret them. The obsolete tz_dsttime field of the => => kernel's timezone value is set to DST_NONE. (For details on what this => => field used to mean, see settimeofday(2).) => => => => This is a good option to use in one of the system startup scripts. => => => => => => > The BIOS time gets adjusted to system time, and then it's wrong. => Exactly => > as described in Eric's first email. => => > => => > ANY IDEAS ???!?!? => => => => Timezones, adjtime, set up bios time (UTC) from the bios itself... => => => -- From Eric (KMail 1.4.3 in Linux, SuSE 8.1) http://www.oh-bugger.net.nz http://homepages.paradise.net.nz/erichard/ NO ATTACHMENT WAS SENT WITH THIS EMAIL IF THERE IS ONE IT IS A UNDETECTED VIRUS, IF THERE IS ONE PLEASE LET ME KNOW ....