> > >If your process gets a signal, read() will return -1 and set
> > >errno to EINTR. You must try the system call again, in a loop,
> > 
> > This does not happen on Linux, at least not when using Libc 5, without
> > undefining GNU or something like that.  The GNU C library by default doesn'
> t
> > interrupt the read or write call when the process receives a signal.
> 
> What does it have to do with the C library? read() is a system call. 

actually, read() is a wrapper for __read(), which is the system call
(glibc-2.0.7-29, RedHat 5.2).
-- 
Kevin L. Mitchell <klmitch@mit.edu>
-------------------------  -. .---- --.. ..- -..-  --------------------------
http://web.mit.edu/klmitch/www/               (PGP keys availiable from here)
    RSA AE87D37D/1024:  DE EA 1E 99 3F 2B F9 23  A0 D8 05 E0 6F BA B9 D2
    DSS ED0DB34E/1024: D9BF 0E74 FDCB 43F5 C597  878F 9455 EC24 ED0D B34E
    DH  2A2C31D4/2048: 1A77 4BA5 9E32 14AE 87DA  9FEC 7106 FC62 2A2C 31D4


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/