aboutsummaryrefslogtreecommitdiffstats
path: root/man7/socket.7
AgeCommit message (Collapse)AuthorFilesLines
2007-04-05ffixMichael Kerrisk1-4/+0
2006-09-26Place socket options in alpha order.Michael Kerrisk1-36/+36
2006-08-03Updated CONFORMING TO sectionMichael Kerrisk1-1/+1
2006-07-21s%IO%I/O%Michael Kerrisk1-3/+3
2006-07-19ffixMichael Kerrisk1-2/+5
2006-05-04Removed FIXMEMichael Kerrisk1-2/+0
2006-03-23Small FIXME formatting fixesMichael Kerrisk1-1/+1
2006-03-15place socket options in alpahbetical orderMichael Kerrisk1-158/+159
2006-03-15ffixMichael Kerrisk1-2/+2
2006-03-15Documented SO_SNDBUFFORCE and SO_RCVBUFFORCE socket options, new in 2.6.14.Michael Kerrisk1-1/+20
2006-03-07Wrap long lines; .ta + TABs with spaces in code examplesMichael Kerrisk1-8/+6
2006-02-10Reformatted FIXMEsMichael Kerrisk1-3/+2
2006-01-13typo fixMichael Kerrisk1-1/+1
2006-01-03Formatting and source code line break changes (no changes to content!)Michael Kerrisk1-11/+13
2005-12-15Noted the Linux-specific feature whereby setsockopt() doublesMichael Kerrisk1-0/+14
the value given for SO_SNDBUF and SO_RCVBUF. Noted kernel imposed minimum values for SO_SNDBUF and SO_RCVBUF.
2005-12-14Updated discussion of SO_BSDCOMPAT.Michael Kerrisk1-15/+19
Reformatted some long lines.
2005-12-13Further refinement of SO_TIMESTAMP from Urs Thuermann.Michael Kerrisk1-6/+10
2005-12-08Von: Urs Thuermann <urs@isnogud.escape.de>Michael Kerrisk1-2/+25
An: "Michael Kerrisk" <mtk-manpages@gmx.net> Betreff: Re: PATCH: man-pages-2.15, socket option SO_TIMESTAMP Datum: 02 Dec 2005 08:00:11 +0100 Hello Michael, > Okay -- let me know if your patch is still good to go after you've > done your reading/testing. Maybe I will try to do another > man-page release tomorrow, if you you can confirm the details in 2.6. I have compared 2.4 and 2.6 src again and wrote two small test programs (one sending udp packets, one receiving the packets and calling SIOCGSTAMP w/ and w/o SO_TIMESTAMP). Both, 2.4 and 2.6 have the same behavior, which may be considered a bug. When a packet is received its timestamp is stored in the sock structure in kernel for SIOCGSTAMP to be retreived if SO_TIMESTAMP is not set, otherwise it is written into a cmsg structure to be returned with the recvmsg syscall. Therefore, SIOCGSTAMP doesn't get the correct timestamp, when SO_TIMESTAMP is set. Instead, SIOCGSTAMP returns an ENOENT error, if there has never been a packet reception while SO_TIMESTAMP unset, since the field in the sock structure in the kernel is initialized to "no timestamp" (0 in 2.4, -1 in 2.6). Otherwise, SIOCGSTAMP returns the timestamp found in the sock structure which is from the last packet when SO_TIMESTAMP was not set, i.e. it may not be the timestamp of the last packet received. I have updated the man page socket(7) accordingly. Patch is below. urs
2005-11-30Added text noting that select()/poll() do no respect SO_RCVLOWAT.Michael Kerrisk1-2/+12
2005-11-15Added FIXME?Michael Kerrisk1-0/+3
2005-11-02Formatting fixesMichael Kerrisk1-5/+5
2005-10-26s/XXX/FIXME/Michael Kerrisk1-1/+1
2005-10-20Formatting fixesMichael Kerrisk1-10/+18
2005-10-19Formatting fixesMichael Kerrisk1-2/+3
2005-10-19Manual fixes for parentheses formattingMichael Kerrisk1-4/+4
2005-10-04Update description of SO_RCVLOWAT and SO_SNDLOWAT.Michael Kerrisk1-8/+9
(fix derived from Fedora man-pages-2.07-7).
2005-08-16Clarified details of use of SO_PEERCRED.Michael Kerrisk1-3/+13
2005-07-18id --> IDMichael Kerrisk1-2/+2
2005-07-06Hyphenation/dash fixesMichael Kerrisk1-1/+1
2005-06-21Minor formatting fixesMichael Kerrisk1-2/+3
2005-06-15global edit s/ -1/ \\-1/gMichael Kerrisk1-1/+1
2004-11-03Global change of email address for MTK (now: mtk-manpages@gmx.net)Michael Kerrisk1-2/+2
2004-11-03Import of man-pages 1.70man-pages-1.70Michael Kerrisk1-0/+588