Re: Setting Up NTP for Time Sync
From: Bill Unruh (unruh_at_physics.ubc.ca)
Date: 01/09/05
- Next message: Michael Fuhr: "Re: listen() and accept()"
- Previous message: W. Watson: "Re: Setting Up NTP for Time Sync"
- In reply to: W. Watson: "Re: Setting Up NTP for Time Sync"
- Next in thread: W. Watson: "Re: Setting Up NTP for Time Sync"
- Reply: W. Watson: "Re: Setting Up NTP for Time Sync"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 9 Jan 2005 07:43:26 -0800 To: "W. Watson" <wolf_tracks@invalid.inv>
On Sun, 9 Jan 2005, W. Watson wrote:
>>>>> Here's my total focus right now. Why can't I synch off of the NTP
>>>>> machine from linux?
>>
>>
>> Again I ask, how do you know that yuour windows machine will act as an NTP
>> server? That is different than acting as an ntp client.
>> I think you have to install ntp server software onto the windows machine.
>>
>>>> 2) Is NTP _server_ installed and configured on XP?
>>>> (how to check this one is up to you. I don't do windows).
>>>
>>> Good question. I was just beginning to look into this at the request of
>>> another posterer, and found via Help a command called net time.
>>> (
>>> Net timeSynchronizes the computer's clock with that of another computer or
>>> domain. Used without parameters, net time displays the time for another
>>> computer or domain.
>>> ...
>>> /querysntp
>>> Displays the name of the Network Time Protocol (NTP) server currently
>>> configured for the local computer or the one specified in ComputerName.
>>> )
I suspect Strongly that it does not. See the web page
http://geodsoft.com/howto/timesync/wininstall.htm
which a) suggests to me that windows does NOT support server, and b)
gives software that you can install which makes it into a server.
Now, whether (NetTime) SNTP will interoperate with NTP on the linux machines I do
not know.
Again, I have no idea what your accuracy requirement is. If it is +- 1
sec, then sntp and your windows solution would be fine. If it is +- ms,
then I would not use the windows solution. ntp is far more thoroughly
implimented on Linux and is set up to correct for the inaccuracies of
the local clock so that even if the connection to the net/servers is
lost for a while (days) the clock still ticks away at the right time.
For systems with sporadic connection to the net, the chronyd is the
better choice. It can also use the on board RTC on the linux machine
(that little clock which keeps ticking via the little on board battery
even if the computer is switched off) to make sure that when you next
switch it on, the time will be accurate-- ie it keeps track of the
offset and the rate errors of the rtc and compensates for them when you
switch on again.
I am still unclear what your topology is. You seems to say that the win
machine has a direct connection to the net, but the Linux machine can
connect only via phone modem but it has a direct connection to the win
machine. Why do you not switch them around. Have the Linux machine have
a direct connection to the net and to the win machine, and then have it
do masquarading for the win machine so it too will have a direct
connection tot he net. Then it can easily act as a time standard for
the win machine, and you will know it is accurate to ms. And both will
have connections to the net.
- Next message: Michael Fuhr: "Re: listen() and accept()"
- Previous message: W. Watson: "Re: Setting Up NTP for Time Sync"
- In reply to: W. Watson: "Re: Setting Up NTP for Time Sync"
- Next in thread: W. Watson: "Re: Setting Up NTP for Time Sync"
- Reply: W. Watson: "Re: Setting Up NTP for Time Sync"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
