Date: Thu, 26 Jan 2012 10:48:17 +0000 (UTC) From: Gleb Smirnoff <glebius@FreeBSD.org> To: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: svn commit: r230578 - head/share/man/man4 Message-ID: <201201261048.q0QAmH2s077413@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: glebius Date: Thu Jan 26 10:48:17 2012 New Revision: 230578 URL: http://svn.freebsd.org/changeset/base/230578 Log: Remove a commented out old block inherited from inet.4. The text there was so much outdated that it required a complete rewrite even for inet.4, not mentioning inet6.4. There is no reason to keep it in the manual page. Modified: head/share/man/man4/inet6.4 Modified: head/share/man/man4/inet6.4 ============================================================================== --- head/share/man/man4/inet6.4 Thu Jan 26 10:43:40 2012 (r230577) +++ head/share/man/man4/inet6.4 Thu Jan 26 10:48:17 2012 (r230578) @@ -184,86 +184,6 @@ by creating an Internet socket of type The .Tn ICMPv6 message protocol is accessible from a raw socket. -.\" .Pp -.\" The 128-bit IPv6 address contains both network and host parts. -.\" However, direct examination of addresses is discouraged. -.\" For those programs which absolutely need to break addresses -.\" into their component parts, the following -.\" .Xr ioctl 2 -.\" commands are provided for a datagram socket in the -.\" .Nm -.\" domain; they have the same form as the -.\" .Dv SIOCIFADDR -.\" command (see -.\" .Xr intro 4 ) . -.\" .Pp -.\" .Bl -tag -width SIOCSIFNETMASK -.\" .It Dv SIOCSIFNETMASK -.\" Set interface network mask. -.\" The network mask defines the network part of the address; -.\" if it contains more of the address than the address type would indicate, -.\" then subnets are in use. -.\" .It Dv SIOCGIFNETMASK -.\" Get interface network mask. -.\" .El -.\" .Sh ROUTING -.\" The current implementation of Internet protocols includes some routing-table -.\" adaptations to provide enhanced caching of certain end-to-end -.\" information necessary for Transaction TCP and Path MTU Discovery. The -.\" following changes are the most significant: -.\" .Bl -enum -.\" .It -.\" All IP routes, except those with the -.\" .Dv RTF_CLONING -.\" flag and those to multicast destinations, have the -.\" .Dv RTF_PRCLONING -.\" flag forcibly enabled (they are thus said to be -.\" .Dq "protocol cloning" ). -.\" .It -.\" When the last reference to an IP route is dropped, the route is -.\" examined to determine if it was created by cloning such a route. If -.\" this is the case, the -.\" .Dv RTF_PROTO3 -.\" flag is turned on, and the expiration timer is initialized to go off -.\" in net.inet.ip.rtexpire seconds. If such a route is re-referenced, -.\" the flag and expiration timer are reset. -.\" .It -.\" A kernel timeout runs once every ten minutes, or sooner if there are -.\" soon-to-expire routes in the kernel routing table, and deletes the -.\" expired routes. -.\" .El -.\" .Pp -.\" A dynamic process is in place to modify the value of -.\" net.inet.ip.rtexpire if the number of cached routes grows too large. -.\" If after an expiration run there are still more than -.\" net.inet.ip.rtmaxcache unreferenced routes remaining, the rtexpire -.\" value is multiplied by 3/4, and any routes which have longer -.\" expiration times have those times adjusted. This process is damped -.\" somewhat by specification of a minimum rtexpire value -.\" (net.inet.ip.rtminexpire), and by restricting the reduction to once in -.\" a ten-minute period. -.\" .Pp -.\" If some external process deletes the original route from which a -.\" protocol-cloned route was generated, the ``child route'' is deleted. -.\" (This is actually a generic mechanism in the routing code support for -.\" protocol-requested cloning.) -.\" .Pp -.\" No attempt is made to manage routes which were not created by protocol -.\" cloning; these are assumed to be static, under the management of an -.\" external routing process, or under the management of a link layer -.\" (e.g., -.\" .Tn ARP -.\" for Ethernets). -.\" .Pp -.\" Only certain types of network activity will result in the cloning of a -.\" route using this mechanism. Specifically, those protocols (such as -.\" .Tn TCP -.\" and -.\" .Tn UDP ) -.\" which themselves cache a long-lasting reference to route for a destination -.\" will trigger the mechanism; whereas raw -.\" .Tn IP -.\" packets, whether locally-generated or forwarded, will not. .Ss MIB Variables A number of variables are implemented in the net.inet6 branch of the .Xr sysctl 3
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201201261048.q0QAmH2s077413>