Messages in this thread | | | Subject | signal behavior and restarting system calls | Date | Sun, 24 Jan 1999 09:54:55 -0800 | From | Stephen Williams <> |
| |
> 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. Its a > nice feature, it allows me to leave out the error handling code that has to > take care of this problem on SunOS and others by restarting the same system > call; adjusted for any changes.
mwood@IUPUI.Edu said: > Very nice, but sadly nonportable. Sounds like we need an all-Unix > conference to hash out an acceptable common solution, unless the > majority really, really loves writing #ifdef s.
Actually, with proper manipulation of sigaction, you get the restart behavior out of SunOS, and I believe most other UNICES as well. I think it is SA_RESTART or somesuch. I forget. -- Steve Williams "The woods are lovely, dark and deep. steve@icarus.com But I have promises to keep, steve@picturel.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep."
- 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/
| |