Interrupted system call on open

[Michael Sperber [Mr. Preprocessor]]

The (revised) patch seems to fix the problem.

>>>>> "Love" == Love  <lha at stacken.kth.se> writes:

Love> sperber at Informatik.Uni-Tuebingen.De (Michael Sperber [Mr. Preprocessor]) writes:

>> It's SIGALRM.  Come to think of it, both Scheme 48 and Netscape (don't 
>> know about Window Maker) use SIGALRM to implement threading.  For
>> Scheme 48, the ktrace output shows zillions of them.

Love> [sending this message to the list also since it explain why it happens]

Love> :(

Love> That isn't good. The xfs-arlad rpc is done in the context of the process
Love> that did the request. If while waiting for the request (in a tsleep) its
Love> aborted (SIGALRM or SIGIO) the RPC is aborted.

Love> The problem is that that if a program have set an alarm it probalably have
Love> a reson to set it, like it doesn't want to wait forever on the filesystem.

Right.  I've looked at the POSIX docs, and the BSD implementation, and
there's nothing in it that says SIGALRM shouldn't be delivered to
open/fopen.  On the other hand, Scheme 48 *does* (and Netscape
probably does) assume that at least fopen won't be interrupted by a
signal.  I personally think that it's a bug in the software, but then
again the software is Netscape ...

So yeah, tough call.

Anyway, I'll file a bug report for Scheme 48 at least.

-- 
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla