man-pages-3.72 is released
Gidday,
The Linux man-pages maintainer proudly announces:
man-pages-3.72 - man pages for Linux
Tarball download:
http://www.kernel.org/doc/man-pages/download.html
Git repository:
https://git.kernel.org/cgit/docs/man-pages/man-pages.git/
Online changelog:
http://man7.org/linux/man-pages/changelog.html#release_3.72
A short summary of the release is blogged at:
http://linux-man-pages.blogspot.com/2014/09/man-pages-372-is-released.html
The current version of the pages is browsable at:
http://man7.org/linux/man-pages/
A few changes in this release that may be of interest to readers of this list are given below.
Cheers,
Michael
==================== Changes in man-pages-3.72 ====================
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
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
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.
Signature · 3 lines
Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
Hello Michael,
Quoted 11 lines · Michael Kerrisk (man-pages)
Gidday,
The Linux man-pages maintainer proudly announces:
man-pages-3.72 - man pages for Linux
Tarball download:
http://www.kernel.org/doc/man-pages/download.html
Git repository:
https://git.kernel.org/cgit/docs/man-pages/man-pages.git/
Online changelog:
Quoted 4 lines
http://man7.org/linux/man-pages/changelog.html#release_3.72A short summary of the release is blogged at:
http://linux-man-pages.blogspot.com/2014/09/man-pages-372-is-released.html
I realized that this this:
https://lkml.org/lkml/2014/6/3/675
(or an equivalent) isn't in shmctl.2. Let me know if you want me to resend/correct anything. Hopefully such information can be added in the near future.
Thanks,
Davidlohr