Re: System clock modified after crash

From: Raj Rijhwani (raj_at_rijhwani.org)
Date: 05/03/04 

Date: Mon, 03 May 2004 22:20:05 +0100 (BST)

On 03 May, in article <87hduxy46e.fsf@sysengr.res.ray.com>
     kullstj-nn@comcast.net "Johan Kullstam" wrote:

> *NO* now you will have both windows *and* linux trying to
> advance/retard the clock at daylight savings time boundaries. Thus
> using local time, in the spring you get the pleasure of seeing windows
> advance the time, boot to linux and see linux advance the time *again*
> and now you are an hour off. Joy.

> In my experience, the only sane way forward is to set your
> CMOS/BIOS/RTC hardware clock to UTC (aka Zulu or Greenwich mean time
> *without* daylight savings adjustment). Linux libc can adjust to your
> locale and show times and dates in your local time. Windows has a
> losing conception of time so they only thing to do is to simply accept
> the lossage and let it lose and resign yourself to the Zulu timestamps
> and clock.

Don't be ridiculous. What's sane about not correcting a fault that's
relatively easily correctable? Windows assumes that the hardware clock is
set to local time. Ok, no big deal - linux can handle local time hardware.
The two can peacefully co-exist entirely happily. Worst case is you'll
need to correct Windows time at, or on first boot after, start/end of
daylight savings time.

> It is also helpful to use NTP. In linux, use ntpdate at boot to set
> your clock, push this time to your hardware clock, then launch ntpd to
> keep it in time. Windows also has a mechanism to poll via NTP to keep
> time set properly (I forget the details but it somehow involves a
> command at the "cmd" prompt). At a first approximation,
> "pool.ntp.org" is the name of the NTP server to use.

Most ISPs have a local NTP server, but using NTP to stabilise is defintitely
a good idea. For NTP client on Windows I use Automachron. 

-- 
Raj Rijhwani                    |  This is the voice of the Mysterons...
raj@rijhwani.org                |  ... We know that you can hear us Earthmen
http://www.rijhwani.org/raj/    |  "Lieutenant Green:  Launch all Angels!"

Relevant Pages

  • Re: Does Fedora mess up the clock for Windows?
    ... the clock to match the NTP server. ... Running the AtomTime95 program under windows would probably make ... Making sure that the time zone is the same under both ...
    (Fedora)
  • Re: Need to implement a calendar clock with millisecond resolution, please help.
    ... clock, not a per-CPU counter, since those may not be or stay in sync. ... I'm confident Windows does provide such a capability, ... standard for this called NTP ... they provide this support for NTP free presumably in the hope that ...
    (comp.lang.c)
  • Re: Clock Problem?
    ... If his system gains a sec per sec ntp can ... Maybe something added something faulty in /etc/adjtime. ... and I've asked him to see if Windows handles the time correctly. ... Unless there is a file that got corrupted by changing the clock by hand ...
    (alt.os.linux.suse)
  • Re: NTP Synchronisation Problem
    ... >> You dont say which version of Windows or include any config files so its ... >> SNTP client to an NTP server. ... >> Time service doesn't take into account clock drift, clock reliability, ...
    (comp.unix.sco.misc)
  • Re: [opensuse] fsck running amok
    ... On Thursday 18 January 2007 14:10, Greg Wallace wrote: ... anywhere I have looked (bios and right clicking the clock in SUSE). ... click the Configure button and I end up in NTP ... I always choose 'Local Time' because I occasionally boot into Windows. ...
    (SuSE)
Loading