Nick Rout wrote:
thats an odd number (well its an even number, but an unusual amount ofProbably to do with the length of the Suse session - it varies a lot, sometimes out by a few hours.
minutes).
Was out by half a day when I tried using GMT(+12). Plain GMT better?
timezones don't go in lots of 40 minutes.
is this a transition thing - like go form suse to windows and back again and something is wrong?
Yes.
the bios clock could be screwy? it should be read on boot, and written back to on shutdown. between boots linux keeps its own clock, either by counting ticks, or with the assistance of ntp etc.
I dunno the exact mechanism on suse, but on gentoo this is handled by the /etc/init.d/clock script, which is started on system startup and stopped on shutdown. maybe suse is not saving the correct time on shutdown? This is the only way the hardware clock gets corrected.
This sounds exactly right.
Chris - I'll try hwclock, but there is no Pacific/Auckland option to choose (!)
Re: tWinkleToes - I've realised I have to keep up with it for my clients / a crust,
+ it came free with my laptop! (never look a gifthorse.. ) ;-\
-- InfoHelp Services http://www.infohelp.co.nz/linux.html i686 2.4.20-8 RedHat Linux 9.0 - Gnome 2.2.0 - OpenOffice 1.0.2 - Mozilla Mail 1.2.1
