Re: [PATCH] making dump EINTR resistant

On  5 Jun, Bruce Evans wrote:

>> Comments?
> 
> read(), etc., are supposed to be restarted after signals, so the EINTR
> checks should have no effect in most cases.

Yes, I wanted to handle it with sigaction & SA_REASTART, but the APUE
book teached me, that signal(3) does restart interrupted syscalls by
default on 4.3(+)BSD. Therefore I handled it with do-while code.

Stevens lists only ioctl, read, readv, write, writev, wait and waitpid,
but not open, fopen, close and fclose. What about those?

- I've seen an EINTR related error once on a 4.x system. I can't
  remember, but I think it was related to an open(2) call.
- Benjamin sees such errors on -current, seems there's something broken.

Bye,
Alexander.

-- 
Actually, Microsoft is sort of a mixture between the Borg and the Ferengi.

http://www.Leidinger.net                       Alexander @ Leidinger.net
  GPG fingerprint = C518 BC70 E67F 143F BE91  3365 79E2 9C60 B006 3FE7


To Unsubscribe: send mail to [email protected]
with "unsubscribe freebsd-audit" in the body of the message