Message116532
| Author |
loewis |
| Recipients |
aronacher, loewis, ned.deily |
| Date |
2010年09月16日.12:13:09 |
| SpamBayes Score |
7.902335e-05 |
| Marked as misclassified |
No |
| Message-id |
<4C9209D3.7050903@v.loewis.de> |
| In-reply-to |
<1284638761.25.0.0187783684302.issue9867@psf.upfronthosting.co.za> |
| Content |
Am 16.09.10 14:06, schrieb Armin Ronacher:
>
> Armin Ronacher<armin.ronacher@active-4.com> added the comment:
>
>> Hmm. So under what conditions should it continue, and under what
>> conditions should it raise an exception (when errno is EINTR)?
>
> EINTR indicates a temporary failure. In that case it should always retry.
But Ruby doesn't. If you send SIGINT, it will print
-e:1:in `read': Interrupt
from -e:1
If you send SIGHUP, it will print
Hangup
So it is surely more complex than "always retry". |
|