From 9910e7ee0a43198d8aaeb25cafb6c61a0e0d0e3d Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Sun, 7 Sep 2014 05:44:50 -0700 Subject: [PATCH] Start of man-pages-3.73: updating Changes and Changes.old --- Changes | 100 +++++---------------------------------------- Changes.old | 115 ++++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 126 insertions(+), 89 deletions(-) diff --git a/Changes b/Changes index b467b4836..3c4973d39 100644 --- a/Changes +++ b/Changes @@ -1,6 +1,6 @@ -==================== Changes in man-pages-3.72 ==================== +==================== Changes in man-pages-3.73 ==================== -Released: 2014-09-07, Mountain View +Released: ????-??-??, Munich Contributors @@ -10,14 +10,6 @@ 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 -Holger Hans Peter Freyther -Michael Haardt -Michael Kerrisk -Mike Frysinger -Peter Schiffer -Rusty Russell -Sorin Dumitru Apologies if I missed anyone! @@ -25,89 +17,19 @@ Apologies if I missed anyone! New and rewritten pages ----------------------- -memusage.1 - Peter Schiffer, Michael Kerrisk [Jan Chaloupka] - New page for glibc memusage(1) command -memusagestat.1 - Peter Schiffer [Jan Chaloupka, Michael Kerrisk] - New page for glibc memusagestat(1) command +Newly documented interfaces in existing pages +--------------------------------------------- -mtrace.1 - Peter Schiffer [Jan Chaloupka] - New page describing the glibc mtrace(1) command + +New and changed links +--------------------- + + +Global changes +-------------- 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 "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 . They are defined in - so we should include that one. diff --git a/Changes.old b/Changes.old index 1ab3bdb65..997948d91 100644 --- a/Changes.old +++ b/Changes.old @@ -33525,3 +33525,118 @@ vdso.7 Add new i386 vdso symbols in Linux 3.15 Michael Kerrisk Note kernel version that exports new i386 symbols (Linux 3.15) + + +==================== Changes in man-pages-3.72 ==================== + +Released: 2014-09-07, Mountain View + + +Contributors +------------ + +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 +Holger Hans Peter Freyther +Michael Haardt +Michael Kerrisk +Mike Frysinger +Peter Schiffer +Rusty Russell +Sorin Dumitru + +Apologies if I missed anyone! + + +New and rewritten pages +----------------------- + +memusage.1 + Peter Schiffer, Michael Kerrisk [Jan Chaloupka] + New page for glibc memusage(1) command + +memusagestat.1 + Peter Schiffer [Jan Chaloupka, Michael Kerrisk] + New page for glibc memusagestat(1) command + +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 "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 . They are defined in + so we should include that one.