Base: Mention that sendfd & recvfd were introduced in plan9port

This commit is contained in:
Sergey Bugaev 2020-06-25 15:23:56 +03:00 committed by Andreas Kling
parent 6efbbcd4ba
commit f08aa6324e
Notes: sideshowbarker 2024-07-19 05:23:46 +09:00
2 changed files with 8 additions and 0 deletions

View file

@ -28,6 +28,10 @@ If a file descriptor is successfully received, it is returned as a non-negative
* `EINVAL`: `sockfd` does not refer to a connected or accepted socket. * `EINVAL`: `sockfd` does not refer to a connected or accepted socket.
* `EAGAIN`: There is no file descriptor queued on this socket. * `EAGAIN`: There is no file descriptor queued on this socket.
## History
`recvfd()` was first introduced in Plan 9 from User Space.
## See also ## See also
* [`sendfd`(2)](sendfd.md) * [`sendfd`(2)](sendfd.md)

View file

@ -29,6 +29,10 @@ If a file descriptor is successfully received, it is returned as a positive inte
* `EINVAL`: `sockfd` does not refer to a connected or accepted socket. * `EINVAL`: `sockfd` does not refer to a connected or accepted socket.
* `EBUSY`: There are too many file descriptors already waiting to be received by the peer. * `EBUSY`: There are too many file descriptors already waiting to be received by the peer.
## History
`sendfd()` was first introduced in Plan 9 from User Space.
## See also ## See also
* [`recvfd`(2)](recvfd.md) * [`recvfd`(2)](recvfd.md)