02/12/02 11:52:53, Ehud Karni <[EMAIL PROTECTED]> wrote: >On Sun, 01 Dec 2002 19:07:50 +0200, voguemaster <[EMAIL PROTECTED]> wrote: >> >> 3. Using SIGALARM. I forgot how this is implemented. Never did go into this since >> it has problems (also among platforms). > >SIGALARM can be used by setting a signal handler (that does nothing). >It functions by interrupting (and thus terminating) the current IO >operation. You activate the timer by calling `alarm' (simpler, whole >seconds) or `setitimer' (more complicated, allow microseconds). I use >both `select' with timeout, and `alarm' in client-server TCP >applications.
Was merely saying I forgot the details of it. Using SIGALARM is a bad scheme for timeouts. > >The ping proves nothing. Most of the ping delay is "computing" delay >caused by the NICs and the switches (and routers and bridges for WAN). >Some of the delay is caused by the bandwidth. Thanks for saying exactly what I did. The ping shows that information on the network doesn't even come close to the speed of light. That was my point. Eli "There's so many different worlds So many different suns And we have just one world But we live in different ones.." - Dire Straits - "Brothers in Arms" ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
