Hi guys. Recently I'm having some serious time issues with my suse 10.2. I have ntp service starting at boot time. Everything was working perfect until recently. It just broke down, each time ntp is starting it displays "Temporary error in name resolution" and the system time and date is set to some strange values (like year 2005 or 2006, random hour and day). I can run ntp after booting is complete and then everything is fine.

I thought it was because network isn't ready so I changed ntp to start as last service, long after network is started. That didn't help. I decided to turn off ntp, since it's not working and still my system time is set to some random value So the first thing I gotta do after booting is setting the correct time. Can anyone give me a clue what is going on and how to fix it? I can provide logs if necessary

It sounds like your hardware clock is wrong at boot. That sets the system time first, then the ntp daemon corrects it. I get the same name resolution error because the network isn't up when ntpd runs, but it does alway set correctly except a couple of times when I had booted into XP and then rebooted Suse, and the clock somehow got set to the wrong time zone. NTP can't always set the clock if the error is large.

Have a look here for info about NTP - http://tf.nist.gov/service/its.htm

My hardware clock is correct - I checked it :/ At the moment ntp is turned off, so shouldn't the kernel read the cmos clock as startup?

I'll have a look at my set-up when I get home. I wonder if your ntp daemon is broken.

My clock isn't right. It shows 06:10 when the time actually is 08:39.

I'm using the Swedish NTP-server to update the time and I haven't gotten an error.

What can I do?

I've tryed to remove the clock from the panel and add it again, but that didn't help.