..
but does signal() interfere with blocking I/O? according to perldelta for version 5.8 if there is no pending I/O (e.g. read is blocking on a socket) then alarm() will interrupt it successfully. but if I/O is pending, the I/O will complete before the alarm() is delivered. this behavior is ok with me. :)
sleep() doesnt interferes with signal() and select()... but signal()
interferes with sleep() and select()...
setting an alarm() sets a timer to deliver the signal SIGALRM to the calling
process after the specified number of second(s)...
but does signal() interfere with blocking I/O? according to perldelta for version 5.8 if there is no pending I/O (e.g. read is blocking on a socket) then alarm() will interrupt it successfully. but if I/O is pending, the I/O will complete before the alarm() is delivered. this behavior is ok with me. :)
_________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
