According to Geoff Hutchison:
> Hmm. The alarm isn't supposed to kill it! The alarm comes from here:
...
> Previously, people reported that the ::connect would never time out,
> or at least until the OS decided to kill off that socket (often quite
> long). So on the advice of a few people, I put in the alarm. Now I
> haven't used alarms too often--am I missing something?
A handler for SIGALRM? I believe the default action is to terminate the
process, so if that's not what you want, you need to set a handler for it.
You should probably take a look at how other TCP/IP clients handle this
situation.
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
