Commit 4a19ec5800fc3bb64e2d87c4d9fdd9e636086fe0 in Jan 2008 added
the new SO_MARK socket option.
This patch is based on text from the commit message.
See https://bugzilla.kernel.org/show_bug.cgi?id=16461.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Fis warning from "groff -ww ..." (or "man --warnings=w ..."):
<groff: mdoc.7>:294: warning:
tab character in unquoted macro argument
In one table the distance between columns is too small in the
"ps" output. (Bug in the groff "doc.tmac" macro?)
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
From "man -ww ..." (groff -ww ...):
<standard input>:541: warning:
tab character in unquoted macro argument
[+3 similar warnings]
<standard input>:813: warning: macro `Pu' not defined
Usage: .Rv -std in sections 2 and 3 only (#1669)
mdoc warning: A .Bl directive has no matching .El (#1821)
String "Pu" defined as a row of punctuation characters.
".Bl" and ".El" fixed.
Some arguments, that start with a period or are the name of a
macro, protected with "\&".
Variable name for macro ".Rv" corrected.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Fix warning from "man ..." ("nroff -ww ..."):
nroff: netlink.7: warning: around line 195:
table wider than line width
Horizontal line incorporated into table.
No right adjustment of text blocks in tables.
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673875
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Fix warning from "man ..." ("nroff -ww ..."):
nroff: rtnetlink.7: warning: around line 415:
table wider than line width
Column gutter reduced to fit line length.
Right adjustment in text blocks removed in tables.
Some header made centered in tables.
One table put on same page.
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674051
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Including <sys/types.h> and <sys/ipc.h> isn't needed on Linux
and isn't really relevant for the explanation on this page.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
There's no need to mention that the 'ipc_perm' structure
is defined in <sys/ipc.h>. That's an implementation detail,
and furthermore <sys/ipc.h> is itself included by the other
System V IPC header files. The current text might lead the
reader to conclude that they must include <sys/ipc.h>, which
is not the case (it is required neither on Linux, nor by the
standards).
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Fix warning from "man ..." ("nroff -ww ..."):
nroff: netdevice.7: warning: around line 98:
table wider than line width
Fix: No right adjustment in text blocks in tables.
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673873
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
man(1) on the present page yields errors:
grotty: ... character above first line discarded
The culprit is "Dl 0 -xxxx" (vertical line) where "xxxx" is
one line (40 nroff units) too long. Or there is a bug in
"grotty". "nroff" or "tbl" makes an empty line where a page is.
The patch fixes the problem by setting the page length to
a large value.
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673436
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
From "nroff -ww -t ...":
warning: around line 44: table wider than line width
Columns are made narrower (column gutter decreased).
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Fix following from "groff -t -ww ...":
warning: around line 53: table wider than line width
Extra indent for "troff" makes the table look misplaced
(default "ps" output).
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Some of the sockets/network protocol pages included names of
the corresponding address family constants in the NAME line,
but this wasn't done consistently across all pages, and probably
it adds little value in those pages that did do this. So, remove
these constants from those pages that have them in the NAME
section.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
It must be a very long time since the statement there
about SIGLOST was true. (The text seems to date back to
1996.)
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This patch clarifies that 0xc0 and 0xc1 are not valid in any UTF-8
encoding[0], and it also references RFC 3629 instead of RFC 2279.
[0] In order to have 0xc0, you'd have to have a two-byte encoding
with all the data bits zero in the first byte (and thus only six
bits of data), which would be an ASCII character encoded in the
non-shortest form. Similarly with 0xc1.
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538641
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
A change in 2.6.28 restored the 2.2 behavior:
https://lkml.org/lkml/2009/6/30/499
Reported-by: lepton <ytht.net@gmail.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
In tcp.7, about TCP_MAXSEG, it reads
If this option is set before connection establishment,
it also changes the MSS value announced to the other
end in the initial packet.
It is correct for kernel version 2.2, but it is not
correct for modern kernel such as 2.4 and 2.6.
On a linux box with a modern kernel, the setting for
TCP_MAXSEG won't change the MSS value announced to the
other end.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Michael Kerrisk