Re: Can EINTR be handled the way BSD handles it? -- a plea from a user-land programmer...

• Next message: Philippe Troin: "Re: 255.255.255.255 won't broadcast to multiple NICs"
• Previous message: george@moberg.com: "Re: Can EINTR be handled the way BSD handles it? -- a plea from a user-land programmer..."
• In reply to: Ulrich Drepper: "Re: Can EINTR be handled the way BSD handles it? -- a plea from a user-land programmer..."
• Next in thread: H. Peter Anvin: "Re: Can EINTR be handled the way BSD handles it? -- a plea from a user-land programmer..."
• Reply: H. Peter Anvin: "Re: Can EINTR be handled the way BSD handles it? -- a plea from a user-land programmer..."
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hello!

> > Can we _PLEASE_PLEASE_PLEASE_ not do this anymore and have the kernel do
> > what BSD does: re-start the interrupted call?
>
> This is crap. Returning EINTR is necessary for many applications.

Just reminder: this "crap" is default behaviour of Linux nowadays. 8)8)

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

• Next message: Philippe Troin: "Re: 255.255.255.255 won't broadcast to multiple NICs"
• Previous message: george@moberg.com: "Re: Can EINTR be handled the way BSD handles it? -- a plea from a user-land programmer..."
• In reply to: Ulrich Drepper: "Re: Can EINTR be handled the way BSD handles it? -- a plea from a user-land programmer..."
• Next in thread: H. Peter Anvin: "Re: Can EINTR be handled the way BSD handles it? -- a plea from a user-land programmer..."
• Reply: H. Peter Anvin: "Re: Can EINTR be handled the way BSD handles it? -- a plea from a user-land programmer..."
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Tue Nov 07 2000 - 21:00:14 EST