mirror of https://github.com/mkerrisk/man-pages
Changes: Ready for 3.72
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
cb7c2ea700
commit
1b679f0a8f
98
Changes
98
Changes
|
@ -1,6 +1,6 @@
|
|||
==================== Changes in man-pages-3.72 ====================
|
||||
|
||||
Released: ????-??-??, Munich
|
||||
Released: ????-??-??, Mountain View
|
||||
|
||||
|
||||
Contributors
|
||||
|
@ -10,6 +10,14 @@ The following people contributed patches/fixes or (noted in brackets
|
|||
in the changelog below) reports, notes, and ideas that have been
|
||||
incorporated in changes in this release:
|
||||
|
||||
Christian von Roques <roques@mti.ag>
|
||||
Holger Hans Peter Freyther <holger@moiji-mobile.com>
|
||||
Michael Haardt <michael@moria.de>
|
||||
Michael Kerrisk <mtk.manpages@gmail.com>
|
||||
Mike Frysinger <vapier@gentoo.org>
|
||||
Peter Schiffer <pschiffe@redhat.com>
|
||||
Rusty Russell <rusty@rustcorp.com.au>
|
||||
Sorin Dumitru <sdumitru@ixiacom.com>
|
||||
|
||||
Apologies if I missed anyone!
|
||||
|
||||
|
@ -17,19 +25,89 @@ Apologies if I missed anyone!
|
|||
New and rewritten pages
|
||||
-----------------------
|
||||
|
||||
memusage.1
|
||||
Peter Schiffer, Michael Kerrisk [Jan Chaloupka]
|
||||
New page for glibc memusage(1) command
|
||||
|
||||
Newly documented interfaces in existing pages
|
||||
---------------------------------------------
|
||||
memusagestat.1
|
||||
Peter Schiffer [Jan Chaloupka, Michael Kerrisk]
|
||||
New page for glibc memusagestat(1) command
|
||||
|
||||
|
||||
New and changed links
|
||||
---------------------
|
||||
|
||||
|
||||
Global changes
|
||||
--------------
|
||||
mtrace.1
|
||||
Peter Schiffer [Jan Chaloupka]
|
||||
New page describing the glibc mtrace(1) command
|
||||
|
||||
|
||||
Changes to individual pages
|
||||
---------------------------
|
||||
|
||||
connect.2
|
||||
Michael Haardt
|
||||
Note that a new socket should be used if connect() fails
|
||||
|
||||
fcntl.2
|
||||
Michael Kerrisk
|
||||
One must define _GNU_SOURCE to get the F_OFD_* definitions
|
||||
|
||||
poll.2, select.2
|
||||
Rusty Russell
|
||||
Fix erroneous description of "available for write".
|
||||
POSIX says: "POLLOUT Normal data may be written without
|
||||
blocking.". This is "may" is misleading, see the POSIX
|
||||
write page:
|
||||
|
||||
Write requests to a pipe or FIFO shall be handled in the
|
||||
same way as a regular file with the following exceptions:
|
||||
...
|
||||
If the O_NONBLOCK flag is clear, a write request may cause
|
||||
the thread to block, but on normal completion it shall
|
||||
return nbyte.
|
||||
...
|
||||
When attempting to write to a file descriptor (other than a
|
||||
pipe or FIFO) that supports non-blocking writes and cannot
|
||||
accept the data immediately:
|
||||
|
||||
If the O_NONBLOCK flag is clear, write() shall block the
|
||||
calling thread until the data can be accepted.
|
||||
|
||||
If the O_NONBLOCK flag is set, write() shall not block the
|
||||
thread. If some data can be written without blocking the
|
||||
thread, write() shall write what it can and return the
|
||||
number of bytes written. Otherwise, it shall return -1 and
|
||||
set errno to [EAGAIN].
|
||||
|
||||
The net result is that write() of more than 1 byte on a
|
||||
socket, pipe or FIFO which is "ready" may block: write()
|
||||
(unlike read!) will attempt to write the entire buffer and
|
||||
only return a short write under exceptional circumstances.
|
||||
|
||||
Indeed, this is the behaviour we see in Linux:
|
||||
|
||||
https://github.com/rustyrussell/ccan/commit/897626152d12d7fd13a8feb36989eb5c8c1f3485
|
||||
https://plus.google.com/103188246877163594460/posts/BkTGTMHDFgZ
|
||||
|
||||
errno.3
|
||||
Michael Kerrisk
|
||||
SEE ALSO: add errno(1)
|
||||
|
||||
rtnetlink.3
|
||||
Holger Hans Peter Freyther
|
||||
Fix parameters for the send() call in the example
|
||||
|
||||
inotify.7
|
||||
Michael Kerrisk
|
||||
IN_OPEN and IN_CLOSE_NOWRITE can also occur for directories
|
||||
Michael Kerrisk
|
||||
IN_CLOSE_WRITE occurs only for files (not monitored directory)
|
||||
Michael Kerrisk
|
||||
IN_MODIFY is generated for files only (not monitored directories)
|
||||
Michael Kerrisk
|
||||
IN_ACCESS occurs only for files inside directories
|
||||
IN_ACCESS does not occur for monitored directory.
|
||||
|
||||
packet.7
|
||||
Sorin Dumitru
|
||||
Fix include file
|
||||
It looks like most of the socket options from this man pages
|
||||
are not defined in <netpacket/packet.h>. They are defined in
|
||||
<linux/if_packet.h> so we should include that one.
|
||||
|
|
Loading…
Reference in New Issue