Bug 20082
Summary: | Please document IP_FREEBIND | ||
---|---|---|---|
Product: | Documentation | Reporter: | Lennart Poettering (mzxreary) |
Component: | man-pages | Assignee: | documentation_man-pages (documentation_man-pages) |
Status: | RESOLVED CODE_FIX | ||
Severity: | normal | CC: | mar-tSIEzQ, mtk.manpages |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | Subsystem: | ||
Regression: | No | Bisected commit-id: |
Description
Lennart Poettering
2010-10-11 14:14:14 UTC
Oh, and there are actually a few more undocumented IP-related sockopts defined in /usr/include/linux/in.h that could use some documentation love. (In reply to comment #0) > IP_FREEBIND is one of my favourite sockopts ;-) , as it allows race-free > listening on any socket without requiring the network interface to be up. > Would > be cool to document this in inet(7). How does the following look? +.TP +.BR IP_FREEBIND " (since Linux 2.4)" +.\" Precisely: 2.4.0-test10 +If enabled, this boolean option allows binding to an IP address +that is nonlocal or does not (yet) exist. +This permits listening on a socket, +without requiring the underlying network interface or the +specified dynamic IP address to be up at the time that +the application is trying to bind to it. +This option is the per-socket equivalent of the +.IR ip_nonlocal_bind +.I /proc +interface described below. (In reply to comment #1) > Oh, and there are actually a few more undocumented IP-related sockopts > defined > in /usr/include/linux/in.h that could use some documentation love. This sounds like one or more separate bug reports... I'll close this now; please reopen if there is still something to be fixed. |