src/lib/libc/sys/accept.2, branch releng/11.3 FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=releng%2F11.3 2014-10-10T03:05:55Z accept(2) may and can return EAGAIN, document it. 2014-10-10T03:05:55Z Xin LI delphij@FreeBSD.org 2014-10-10T03:05:55Z urn:sha1:b888b86e6f8361c87b31e700d2a16ff1c9e0b155 MFC after: 1 week Add some missing .Nm for newer syscalls in existing man pages. 2014-01-11T22:00:16Z Jilles Tjoelker jilles@FreeBSD.org 2014-01-11T22:00:16Z urn:sha1:b83686c8fed09dcfd3629daf07fcc38560b766a6 MFC after: 1 week accept(2): Update portability note for accept4(). 2013-10-01T21:17:18Z Jilles Tjoelker jilles@FreeBSD.org 2013-10-01T21:17:18Z urn:sha1:0f49c96cfc484c26d9153727b7d929d1e353993e The accept(2) man page warns that O_NONBLOCK and other properties on the new socket may vary across implementations. However, this issue only applies to accept() and not to accept4(). On the other hand, accept4() is not commonly available yet. Reported by: pluknet Reviewed by: bjk Approved by: re (kib) accept(2), pipe(2): Fix .Dd. 2013-05-01T22:47:47Z Jilles Tjoelker jilles@FreeBSD.org 2013-05-01T22:47:47Z urn:sha1:ed5987bd08dc2bcf9ce6d5d20caaf683cea00ba5 Add accept4() system call. 2013-05-01T20:10:21Z Jilles Tjoelker jilles@FreeBSD.org 2013-05-01T20:10:21Z urn:sha1:da7d2afb6d25a50559173e51f4b3044656a587fb The accept4() function, compared to accept(), allows setting the new file descriptor atomically close-on-exec and explicitly controlling the non-blocking status on the new socket. (Note that the latter point means that accept() is not equivalent to any form of accept4().) The linuxulator's accept4 implementation leaves a race window where the new file descriptor is not close-on-exec because it calls sys_accept(). This implementation leaves no such race window (by using falloc() flags). The linuxulator could be fixed and simplified by using the new code. Like accept(), accept4() is async-signal-safe, a cancellation point and permitted in capability mode. Keep up with negative addrlen check removal in r249649. 2013-04-22T09:18:50Z Sergey Kandaurov pluknet@FreeBSD.org 2013-04-22T09:18:50Z urn:sha1:89bbe1496df25bd8dc35f22a6212796743a45a56 accept(2): Mention inheritance of O_ASYNC and signal destination. 2013-03-26T22:46:56Z Jilles Tjoelker jilles@FreeBSD.org 2013-03-26T22:46:56Z urn:sha1:de9dcfba063ba8dde86ba61a7ea6ab3d5a6bb2d5 While almost nobody uses O_ASYNC, and rightly so, the inheritance of the related properties across accept() is a portability issue like the inheritance of O_NONBLOCK. Attempt to reduce accidental foot-shooting by pointing out that 2009-11-02T07:21:13Z Colin Percival cperciva@FreeBSD.org 2009-11-02T07:21:13Z urn:sha1:4054af4fb0fcdc6115601d6b27cc5dd3a7875da6 accept(2)ed sockets do not necessarily inherit O_NONBLOCK from listening sockets on non-FreeBSD platforms. Feet shot: cperciva MFC after: 1 month Add Xr to getsockname(2) 2008-06-20T14:47:06Z Poul-Henning Kamp phk@FreeBSD.org 2008-06-20T14:47:06Z urn:sha1:20067a6892715483fed56741020e6561d40ac091 Per Regents of the University of Calfornia letter, remove advertising 2007-01-09T00:28:16Z Warner Losh imp@FreeBSD.org 2007-01-09T00:28:16Z urn:sha1:c879ae3536e6d92b8d96c8965c5b05fcb9541520 clause. # If I've done so improperly on a file, please let me know.