Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
fcntl.2, getitimer.2, inotify_add_watch.2, open.2, pipe.2, poll.2, sendmmsg.2, set_tid_address.2, shmop.2, signalfd.2, splice.2, syscalls.2, syslog.2, tee.2, vmsplice.2, ether_aton.3, mallopt.3, printf.3, profil.3, charmap.5, proc.5, epoll.7, inotify.7, libc.7, pipe.7, sched.7, socket.7, udplite.7, iconvconfig.8, ld.so.8: tstamp
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Reviewed-by: Marko Myllynen <myllynen@redhat.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
The LD_PROFILE output is appended to any existing
contents of the target file.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Really, with respect to watched directories, events fall into
three classes (not two, as was shown):
* Events that can be generated only for the watched directory.
* Events that can be generated only for objects that are inside
the watched directory.
* Events that can be generated both for the watched directory
and for objects inside the directory.
So, mark these three classes more clearly in the list of inotify
events.
dd
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Reported-by: Walter Harms <wharms@bfs.de>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
In fcntl(2) F_SETPIPE_SZ, F_GETPIPE_SZ and /proc/sys/fs/pipe-max-size are
defined, however pipe(7) still defines the pipe capacity as being a static
entity. Adding a reference to fcntl(2).
Signed-off-by: Elie De Brauwer <eliedebrauwer@gmail.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
To make use of PIPE_BUF in an application one should include limits.h.
Adding a reference to this inclusion.
Signed-off-by: Elie De Brauwer <eliedebrauwer@gmail.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
If the caller does not have CAP_BLOCK_SUSPEND, then EPOLLWAKEUP
is silently ignored.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Reported-by: Rich Felker <dalias@libc.org>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
See https://bugzilla.kernel.org/show_bug.cgi?id=79411
Reported-by: Nadav Har'El <nyh@math.technion.ac.il>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Reported-by: Tomi Salminen <tlsalmin@gmail.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
programs
My testing on this point was bogus, overlooking details of
strace(1)'s behavior with setuid programs.
See https://sourceware.org/bugzilla/show_bug.cgi?id=12155
Reported-by: Florian Weimer <fweimer@redhat.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
And propose a workaround if the caller cares about catching
close() time errors.
See http://stackoverflow.com/questions/23440216/race-condition-when-using-dup2#comment36888604_23444465
and http://austingroupbugs.net/view.php?id=411
Reported-by: Rich Felker <dalias@libc.org>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
In particular, note that dup2() performs the steps of closing
and reusing 'newfd' atomically.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
We probably don't now need such ancient info.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Rich Felker noted that "scare text" in the man page warned about
the use of snprintf() on libc, and that some people had cited
this as a reason not to use snprintf(). Linux libc is now
ancient history, so there is no real need to keep that text.
But, while we're at it, we may as well clear out all of the
other ancient libc4 and libc5 pieces in the page. They are
nowadays more clutter than help.
Reported-by: Rich Felker <dalias@libc.org>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Determined by inspection of the SUSv3 and SUSv4 specifications.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Make it clearer that the target of monitoring is an i-node,
not a pathname.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Clarify the text a little, in particular making it clearer
that the target of a watch is an i-node (not a pathname).
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|
|
The target of a watch is an i-node, not a pathname. Clarify
the text to prevent the reader possibly misunderstanding
that establishing watches by two different links to the same
file might create different watch descriptors.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
|