On Sat, 27 Mar 2010 at 8:14:07 +0200, Johann Haarhoff wrote: > > > >Why was the op interrupted? Retrying the op ignores the intent of the > >signal. Or is there a problem with spurious signals? > > Any system call in UNIX is allowed to be interrupted by EINTR. > It is neither spurious or an error. As far as I can tell the > correct behavior is to retry. If there really is an error you will > get an error other than EINTR. I do not think this will cause an infinite > loop.
[...] > But I would not bother reporting the "error" since a system call being > interrupted by a signal is not really an error condition, it's just a > normal UNIX event. If you get an error return and errno is EINTR, just > restart the loop as if nothing happened. > > In fact, many UNIX system calls can be interrupted by signals, and you should > generally always check for EINTR and retry the system call." Ok, this is the kind of thing I wanted to know before applying. I applied the patch now. Thanks everyone! -- To unsubscribe, send mail to [email protected].
