IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New Time synchronization?
We've got a combination of Win2000, Solaris, and Linux here. What do y'all think would be the best way to do very accurate time synchronization for things like source code repositories and build management?
Regards,

-scott anderson
New How accurate?
I use a freeware SNTP app which gets time from a time server every hour. Depending on the PC, the time can be off by a second or so before it's adjusted.

Look for cmdtime (the copy I got was from [link|http://www.softshape.com/download/#freeware|softshape.com] for Win32) or something similar. Lots of similar things for *nix and OS/2.

If you need better resolution, you might need something else...

HTH.

Cheers,
Scott.
New I'd prefer sub-second accuracy
With a large number of developers checking in code from multiple machines, those seconds can add up.
Regards,

-scott anderson
New Local radio clock
And have the boxes synchronise against your own local NTP server.

I think you get +/- 0.5sec accuracy with NTP.


Peter
Shill For Hire
[link|http://www.kuro5hin.org|There is no K5 Cabal]
New Does that work for W2K/AS?
One of the admins here mentioned that AS needs time synch, so we have some internal Win2K synch servers...
Regards,

-scott anderson
New Re: Does that work for W2K/AS?
You mean Active Directory, I take it.

The Windows 2000 time service can obtain its time from a regular NTP server, yes.



Peter
Shill For Hire
[link|http://www.kuro5hin.org|There is no K5 Cabal]
New Addendum
W32Time actually uses SNTP, not NTP, so doesn't have all the bells and whistles. But if it's accurate enough for Kerberos (shut up now before you start (:= ) authentication, I think it'll be accurate enough to stop your CVS repository getting munged.


Peter
Shill For Hire
[link|http://www.kuro5hin.org|There is no K5 Cabal]
New As it turns out...
They've got the Solaris boxen and the W2K boxen synched somehow, and I was told to just use rdate against one of the development boxes. :-)

Thanks.
Regards,

-scott anderson
New ntp / ntpdate
I run these on my systems. One box is the local timeserver. It syncs against a number of outside servers. Accuracy is well under 1 second, [link|http://www.uwsg.iu.edu/hypermail/linux/kernel/9812.0/0306.html|kernel mail] from Peter Anvin suggests 200 - 50 microsecond accuracy (+/- 0.2-0.05 seconds). Relevant RFCs: 1305, 1059, and 1119.

Solaris is going to have something similar, not sure of NT.
--
Karsten M. Self [link|mailto:kmself@ix.netcom.com|kmself@ix.netcom.com]
What part of "gestalt" don't you understand?
New ntp/ntpdate has been around solaris fer years
tshirt front "born to die before I get old"
thshirt back "fscked another one didnja?"
     Time synchronization? - (admin) - (9)
         How accurate? - (Another Scott) - (6)
             I'd prefer sub-second accuracy - (admin) - (5)
                 Local radio clock - (pwhysall) - (4)
                     Does that work for W2K/AS? - (admin) - (2)
                         Re: Does that work for W2K/AS? - (pwhysall) - (1)
                             Addendum - (pwhysall)
                     As it turns out... - (admin)
         ntp / ntpdate - (kmself) - (1)
             ntp/ntpdate has been around solaris fer years -NT - (boxley)

WORA
158 ms