Found these references if any help

http://tldp.org/HOWTO/TimePrecision-HOWTO/set.html
http://avi.alkalay.net/linux/docs/TimePrecision/TimePrecision.html

The second talks about chrony which I've never heard of as a way of keeping
your machine time accurate if you don't have ntp running. Here's a snippet

. Precise Time with the chrony Program

6.1. How chrony Differs from the ntp Suite?

chrony also uses the NTP protocol, and is also designed to make Linux clock more accurate. It is also suitable for systems that do not have an Internet connection. Then the source of the exact time can be any accurate clock, from which we can read the time and type it to the program. In addition, it is also capable of calculating the inaccuracy of the hardware clock, and based on that, adjust the hardware clock at boot time.

chrony 1.20 does not support built-in hardware clocks like GPS and DCF receivers, but the structure of the program makes such development possible.

6.2. How to Use chrony?

chrony consists of two parts: chronyd daemon and a user interface chronyc.

You can find chrony at chrony.sunsite.dk/index.php




Neill Jones wrote:
Hi all

I've set NTP on using the DrakClock panel applet which doesn't offer
the BIOS setting that Ron mentions, however I don't get any problem
with the Windows and Linux clocks being off, so I guess it sets it
correctly as default. This asks you for the disks to install the NTP software
and I just installed that without any changes. Hope that works for you

Neill

Ron Hunter-Duvar wrote:
On April 17, 2006 13:40, Keith Powell wrote:
...
  
I can find no way of getting Linux (except for SUSE, which allows one
to chose between UTC and local) to cope with the BIOS clock being set
to local time, or for XP to cope with the BIOS clock being set to UTC
and not changing it.
    
...

I can't guarantee this works, but in Mandriva when you configure ntp (assuming 
you're using ntp), there's an option to tell it whether the BIOS clock is set 
to UTC or local time. It's recommended that you use the local time setting 
when dual booting, because this is what Windoze expects. This should allow 
you to see the correct time in both OS's year round. 

But like dch mentioned, you might have to be careful about which OS handles 
the summer/winter time change. I think ntp would be smart enough to know 
whether the time has been changed and handle it appropriately (because it 
compares your clock against an external UTC clock, and knows your timezone). 
But if ntp made the change, and then Windoze made the change again, you'd be 
off again. Even then, you'll only need to fix it twice a year 8^).

  

Reply via email to