On Sat, 10 Aug 2002 00:07:28 +0100 Ian Dowse <[EMAIL PROTECTED]>

> I was just looking at PR bin/18319 when I remembered this message.
> Many of the changes in your patch are not necessary I believe, as
> read(2) will restart after a signal by default. How about just
> fixing the open call that actually triggers the reported error? I
> suspect that many of the other cases are either impossible or
> extremely unlikely in practice. Could someone who can reproduce the
> "couldn't reopen disk" error try the following?

Have a look at Message-ID: <[EMAIL PROTECTED]>
(should be in the archive of audit).

Short: open shouldn't be able to return EINTR in practice...

My assumptions:
 - Bruce hasn't made a mistake
 - something broke in the kernel (either for a "short" period of
   time, or it's still broken), so we should look for the real
   problem instead


           Intel: where Quality is job number 0.9998782345!

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-current" in the body of the message

Reply via email to