Messages in this thread | | | Subject | Re: [PATCH] Wrong errno out of memory in open syscall | Date | Fri, 28 Jan 2000 20:17:12 -0500 | From | "Brandon S. Allbery KF8NH" <> |
| |
In message <20000129012828.A2531@win.tue.nl>, Guest section DW writes: +----- | What version of System V is this? I have a handful of System V manuals, | but mine either do not list EAGAIN at all (for open()) or describe it | by "the path argument names the slave side of a pseudo-terminal device | that is locked". Or is this undocumented behaviour? +--->8
It appears to be undocumented, or possibly SVR4 reverted this behavior. Back when I herded SVR3.[12] systems, EAGAIN could be produced by just about any system call that encountered a "transient out of resources" condition in the kernel; this wasn't always documented in affected system calls, but was at the time documented in intro(2).
Solaris appears to use EAGAIN only for "out of processes/LWPs" according to its intro(2), so either it or SVR4 in general appears to have moved away from that behavior. I don't see any equivalents to the SVR3 EAGAIN behavior in its intro(2); maybe SVR4 puts the process to sleep until there are sufficient resources?
-- brandon s. allbery os/2,linux,solaris,perl allbery@kf8nh.apk.net system administrator kthkrb,heimdal,gnome,rt allbery@ece.cmu.edu carnegie mellon / electrical and computer engineering kf8nh We are Linux. Resistance is an indication that you missed the point.
- 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/
| |