Hi, Well, sync on ns1.gnu.org instead of cron'd ntpdate was a suggestion from the FSF sysadmins in the first place ;) (can't remember who).
I guess we'll do things differently. Curiously despite the ntpdc output, Savannah was 30s late, I can't see why. -- Sylvain On Mon, Mar 12, 2007 at 11:40:20AM -0400, Joshua Ginsberg via RT wrote: > farrokh:~# ntpdate time.nist.gov > > 12 Mar 11:36:51 ntpdate[20471]: adjust time server 192.43.244.18 offset > -0.018452 sec > > > farrokh == ns1.gnu.org > > Even still, I'd recommend you switch to using time.nist.gov -- we don't > actually invest any effort into having an authoritative time service. > > -jag > > > [beuc - Sun Mar 11 14:30:09 2007]: > > > > Hello sysadmins, > > > > Greg suggests that the Savannah clock, which is sync'd with > > ns1.gnu.org, is a bit late (~20secs). > > > > I indeed note a difference between by computer and sv: > > me# LANG=C date -u +%c > > Sun Mar 11 18:28:07 2007 > > sv# LANG=C date -u +%c > > Sun Mar 11 18:27:41 2007 > > > > The NTP connection looks good afaics: > > savannah:~# ntpdc > > ntpdc> peers > > remote local st poll reach delay offset disp > > ======================================================================= > > =ns1.gnu.org 199.232.41.3 16 1024 0 0.00000 0.000000 0.00000 > > > > So maybe ns1.gnu.org's hour is a bit late. > > > > Can you have a look at it? > > > > Thanks, > > > > > > > -- > Joshua Ginsberg <[EMAIL PROTECTED]> > Free Software Foundation - Senior Systems Administrator >
