Commit Graph

727 Commits

Author SHA1 Message Date
Michael Kerrisk 5059acc358 Remove text under EINVAL error: "This may change in the future:
see linux/unix/sock.c for details."  This behaviour has been
unchanged for a long time, and seems unlikely to change.

Add EADDRINUSE to errors.
2005-12-19 10:46:01 +00:00
Michael Kerrisk 89cc227528 Formatting fix 2005-12-19 10:33:47 +00:00
Michael Kerrisk 1df419f2b7 Add cmsg.3 to SEE ALSO. 2005-12-19 09:16:57 +00:00
Michael Kerrisk a30e090e7c Added description of 'x' mode character (exclusive open). 2005-12-15 15:58:16 +00:00
Michael Kerrisk a88415fa5b Start of 2.19 2005-12-15 13:15:05 +00:00
Michael Kerrisk de544c10e1 Start of 2.19 2005-12-15 13:12:41 +00:00
Michael Kerrisk 66d75ec9ca Ready for 2.18 2005-12-15 13:05:51 +00:00
Michael Kerrisk 8d5bf1790f Undo accidental deletion of many lines! 2005-12-15 13:04:00 +00:00
Michael Kerrisk 65cb02b927 Ready for 2.18. 2005-12-15 12:57:49 +00:00
Michael Kerrisk f406c335ef Noted details of SO_SNBUF and SO_RCVBUF support for Unix domain sockets. 2005-12-15 12:46:18 +00:00
Michael Kerrisk 17805f5b31 Noted the Linux-specific feature whereby setsockopt() doubles
the value given for SO_SNDBUF and SO_RCVBUF.

Noted kernel imposed minimum values for SO_SNDBUF and SO_RCVBUF.
2005-12-15 12:36:08 +00:00
Michael Kerrisk 69c4c18902 updated FIXME 2005-12-14 16:46:05 +00:00
Michael Kerrisk 512c311c5e Put 'flags' list in alphabetical order. 2005-12-14 16:44:39 +00:00
Michael Kerrisk a28ed21cec Put flags list in alphabetcal order 2005-12-14 16:41:14 +00:00
Michael Kerrisk 8609725360 Added new (UN)SUPPORTED FEATURES section in which it is noted
that Unix domain sockets do not support MSG_OOB or MSG_MORE.
2005-12-14 16:36:17 +00:00
Michael Kerrisk 145ff0249e Added cross-reference from discussion of MSG_MORE to UDP_CORK in udp(7). 2005-12-14 16:30:49 +00:00
Michael Kerrisk 8b9d679941 Add + to unary operator list 2005-12-14 12:50:57 +00:00
Michael Kerrisk d7871cf963 Added err(3) to SEE ALSO 2005-12-14 12:09:39 +00:00
Michael Kerrisk 26b66d19a9 Added CONFORMING TO section noting that these are non-standard BSDisms. 2005-12-14 12:08:59 +00:00
Michael Kerrisk 711672c037 ffix 2005-12-14 11:40:27 +00:00
Michael Kerrisk ffa01655e5 Added mention of AF_INET6 address family.
Added discussion of sockaddr structure and an example in the Unix domain.
2005-12-14 11:37:28 +00:00
Michael Kerrisk a917b0bb2c Small wording changes around discussion of SO_BSDCOMPAT.
Fixed a couple of wording errors elsewhere.
Reformatted some long lines.
2005-12-14 10:27:45 +00:00
Michael Kerrisk 514d7e5b92 Updated discussion of SO_BSDCOMPAT.
Reformatted some long lines.
2005-12-14 10:27:30 +00:00
Michael Kerrisk 9ae132041b Updated discussion of SO_BSDCOMPAT. 2005-12-14 10:27:10 +00:00
Michael Kerrisk ed07f09aeb A few refinments to recent changes 2005-12-14 09:27:17 +00:00
Michael Kerrisk aca9215859 dded resolver(5) to SEE ALSO 2005-12-13 18:42:35 +00:00
Michael Kerrisk 6e84dfa12a Rewrote and extended the discussion of the two flavours of
strerror_r(), and added some additional information on strerror().
2005-12-13 18:42:16 +00:00
Michael Kerrisk ac1056b5c0 Remove cross references to resolv+(8); add cross references to
resolv.conf(5).  (See also Debian Bug#214892)
2005-12-13 15:23:07 +00:00
Michael Kerrisk 24268a723c Added references to nsswitch.conf(5); remove cross references
to resolv+(8)
2005-12-13 15:22:17 +00:00
Michael Kerrisk b2e302ec2f Formatting fix 2005-12-13 14:20:45 +00:00
Michael Kerrisk 855b75c6a3 Fix three typos in identifier names. 2005-12-13 13:36:17 +00:00
Michael Kerrisk 9c7e8803dd Start of 2.18 2005-12-13 13:31:44 +00:00
Michael Kerrisk 374c03a8b4 Start of 2.18 2005-12-13 13:29:14 +00:00
Michael Kerrisk f8858ae992 Ready for 2.17 2005-12-13 11:27:22 +00:00
Michael Kerrisk 9e809d86f5 Ready for 2.17 2005-12-13 11:25:04 +00:00
Michael Kerrisk 4ccef6766d Ready for 2.17 2005-12-13 11:22:52 +00:00
Michael Kerrisk 7199370f3a Further refinement of SO_TIMESTAMP from Urs Thuermann. 2005-12-13 10:46:50 +00:00
Michael Kerrisk 010b1b8e1c Typo fix 2005-12-12 09:27:49 +00:00
Michael Kerrisk cde9f44b19 Added comment noting that fork.2 refers to the example program on this
page.
2005-12-12 09:19:46 +00:00
Michael Kerrisk d7b0e083ce Added xref to pipe.2 for another example of use of fork(). 2005-12-12 09:18:35 +00:00
Michael Kerrisk bb001e259b minor chgs 2005-12-12 09:17:47 +00:00
Michael Kerrisk 2d1af8c71a Added test on EXAMPLE PROGRAMS 2005-12-12 09:16:33 +00:00
Michael Kerrisk 8440a332f7 Formatting fix 2005-12-09 16:37:46 +00:00
Michael Kerrisk 1fa343d1ab Added example program demonstrating use of fork() and waitpid(). 2005-12-09 16:37:05 +00:00
Michael Kerrisk 2f59b1bc3c Added pointer to example of fork() in wait.2. 2005-12-09 16:36:12 +00:00
Michael Kerrisk 15740f8afd Added example program. 2005-12-09 14:24:10 +00:00
Michael Kerrisk 48afe71d57 Improvements after suggestions from Michael Haardt. 2005-12-09 14:23:53 +00:00
Michael Kerrisk be37f2c558 Added SEE ALSO for new pipe.7 page 2005-12-08 18:57:25 +00:00
Michael Kerrisk 2adb3bd6da New page providing overview of pipes and FIFOs. 2005-12-08 18:52:42 +00:00
Michael Kerrisk 7b5c3d0a78 Von: Urs Thuermann <urs@isnogud.escape.de>
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-12-08 16:36:30 +00:00