Messages in this thread | | | From | "Anthony Barbachan" <> | Subject | Re: User vs. Kernel (was: To be smug, or not to be smug, that is the | Date | Fri, 22 Jan 1999 23:41:28 -0500 |
| |
-----Original Message----- From: Steve Dodd <dirk@loth.demon.co.uk> To: linux-kernel@vger.rutgers.edu <linux-kernel@vger.rutgers.edu> Date: Friday, January 22, 1999 9:24 PM Subject: Re: User vs. Kernel (was: To be smug, or not to be smug, that is the
>Hi, > >On Fri, Jan 22, 1999 at 01:15:42AM -0500, Anthony Barbachan wrote: > >> >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.
But its not called directly, the read function in the C library is called first. Check the info docs on libc 5 (probably 6, but not sure) this change in behavior is noted.
> >S. > >-- >If breastfeeding a pig is sickening to you, what the hell are you >doing on usenet? -- Aimee, on rec.music.tori-amos > >- >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/ > >
- 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/
| |