Since Linux 3.4 there appeared an ability to specify the
offset in bytes from which the data will be MSG_PEEK-ed.
Describe this socket option in the socket(7) page, where
all the other socket options are described.
Signed-off-by: Pavel Emelyanov <xemul@parallels.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
POSIX.1-2001 does not specify the behavior in this case
and no other system that I checked documented the behavior.
Probably, most or all systems do what Linux does in this
case: cancel any pending alarm, just as alarm(0) does.
Add that info in NOTES.
Reported-by: Nicolas Hillegeer <nicolas@hillegeer.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This directory was added in Linux v3.3 and provides info about
files being mmap-ed in a way very similar to how /proc/[pid]/fd
works.
v2: Added examples of how links look like and noted dependency
on kernel config option CONFIG_CHECKPOINT_RESTORE.
Signed-off-by: Pavel Emelyanov <xemul@parallels.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The description of ia64 clone2() should follow the discussion
of the raw system call interface.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
And further clarify the distinction between the system call
and the wrapper function in the introductory text.
Reported-by: Peter Schiffer <pschiffe@redhat.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit adds documentation for the IP_MULTICAST_ALL socket
option.
The option was added to the Linux kernel in 2.6.31:
Author Nivedita Singhvi <niv@us.ibm.com>
Commit f771bef98004d9d141b085d987a77d06669d4f4f
The description is based on a previous one [3] posted by the
original author of the code -- Nivedita, but it is slightly
re-worded.
I tested it myself and it works as described.
References:
[1] http://lxr.free-electrons.com/source/net/ipv4/ip_sockglue.c#L972
[2] http://lxr.free-electrons.com/source/net/ipv4/igmp.c#L2267
[3] http://patchwork.ozlabs.org/patch/28902/
Signed-off-by: Radek Pazdera <rpazdera@redhat.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The description was rather vague, citing a "list of I/O contexts"
and stating that it "can" cancel outstanding requests. This
update makes things more concrete so that the reader knows exactly
what's going on.
Signed-off-by: Jeff Moyer <jmoyer@redhat.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
nr_events is technically the number of completion events that can
be stored in the completion ring. The wording of the man page:
"capable of receiving at least nr_events" seems dubious to me,
only because I worry that folks might interpret that to mean
'nr_events' total, instead of 'nr_events' concurrently.
Further, I've added information on where to find the per-user
limit on 'nr_events', /proc/sys/fs/aio-max-nr. Let me know if
you think that is not relevant.
Signed-off-by: Jeff Moyer <jmoyer@redhat.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
I looked back through the kernel code, and the timeout was
never updated in any case. I've submitted a patch upstream
to change the comment above io_getevents.
Signed-off-by: Jeff Moyer <jmoyer@redhat.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
When describing e_ident, most of the EI_xxx defines mention the
exact byte number. This is useful when manually hacking an ELF
with a hex editor. However, the last few fields don't do this,
which means you have to count things up yourself.
Add a single word to each so you don't have to do that.
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Split into tables so that the information does not render wider
than 80 columns. Add some explanation of tables and table columns.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Michael Kerrisk