Uhm...what's this? [rdate question]

Tom 'Needs A Hat' Mitchell mitch48 at sbcglobal.net
Mon Apr 5 16:33:46 UTC 2004


On Sun, Apr 04, 2004 at 05:39:45PM -0500, Robert wrote:
> Brian Fahrlander wrote:
> >    My local clock got moved, so I used redhat-config-time to establish
> >a new one.  Then, just in case it'd take all day to adjust it via NTP, I
> >ran:
> >
> >[root at aquila root]# rdate -s time.nist.gov
> >Alarm clock
> >
> >    ..."Alarm clock"?  What the heck?
> >
> >
> 
> It looks like time.nist.gov has been out to lunch all weekend.

At the end of an strace of rdate -s time.nist.gov I see:

  5863  connect(3, {sa_family=AF_INET, sin_port=htons(37), sin_addr=inet_addr("192.43.244.18")}, 16) = ? ERESTARTSYS (To be restarted)
  5863  --- SIGALRM (Alarm clock) @ 0 (0) ---
  5863  +++ killed by SIGALRM +++

I suspect that there is a time-out built into rdate that is getting
triggered.  Since this the weekend that daylight saving time switched
here I bet the site was being hit bunches.

I guess I could look at the source and ... naw guessing
is too much fun.  ;-)




-- 
	T o m  M i t c h e l l 
	/dev/null the ultimate in secure storage.





More information about the fedora-list mailing list