thats an odd number (well its an even number, but an unusual amount of minutes).
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? 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. On Mon, 17 May 2004 15:42:11 +1200 InfoHelp <[EMAIL PROTECTED]> wrote: > True, but not 40 > > Nick Rout wrote: > > >On Mon, 17 May 2004 15:39:00 +1200 > >InfoHelp <[EMAIL PROTECTED]> wrote: > > > > > > > >>>what makes u think suse has a problem? > >>> > >>> > >>> > >>Every time I start it up, the clock is out. > >>Tried a few settings, no change. > >>Currently on Time Zone: Global - NZ which is reducing errors from hours > >>to minutes. > >> > >> > > > >how much is it out by? its likely to be out by a minute or two. > > > > > -- > 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 > -- Nick Rout <[EMAIL PROTECTED]>
