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

[Brian Fahrlander]

On Mon, 2004-04-05 at 11:33, Tom 'Needs A Hat' Mitchell wrote:

> 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.  ;-)

    Good man! You found a reason where once there was none.  Kudos.

    Will the source, though, say why they picked "Alarm clock" as a
diagnostic instead of "Time source overloaded" or "Time not available"? 

    Hackers.  Good or bad, they're always a couple of degrees askew from
the rest of the world.  :>

-- 
------------------------------------------------------------------------
Brian Fahrländer          GNU/Linux Zealot, Conservative, and Technomad
Evansville, IN                    My Voyage: http://www.CounterMoon.com 
ICQ 5119262
------------------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://listman.redhat.com/archives/fedora-list/attachments/20040405/1e433ea7/attachment-0001.sig>