Re: accept() and signals

[crincon@et.com.mx (Cesar Rincon)]

Ipsissima verba Glynn Clements:
> The default behaviour of signal() in GNU libc 2.x is the BSD
> behaviour, i.e. interrupted system calls are automatically
> restarted, and the handler isn't reset upon receipt of a signal. If
> you want system calls such as accept() to be interrupted, you should
> use sigaction() without the SA_RESTART flag.

Which works perfectly, thank you very much.

> More generally, the safest approach is to always use sigaction()
> rather than to assume a particular behaviour from signal().

And it says that much in the manual, duh.  It's just that I was using
Spanish-translated dev manpages, which are, now I know, ahem, a bit
outdated.  E.g., sigaction(2) says that SA_RESETHAND is the default
behaviour of signal()...

Oh, well.  Firing up a mail to the translators.

Thanks again.

 -CR

-- 
Ceterum censeo: SCO delenda est.