to have the $FreeBSD$ keyword, as this is now enforced
by the CVSROOT/commit_prep.pl script.
Fold multi-word macro arguments into a single argument
by putting the surrounding double quotes - this speeds
up the -mdoc processing drastically (of course if used
systematically).
Use the new features of -mdoc: exact -width specifiers,
.In macro as an ``.Fd #include'' replacement.
directory does not exist, instead of creating/overwriting a file
with the name of the (expected) directory. Yes, this deviates a bit
from nearly all other install targets in the tree, but let's face it,
removing a modules directory is not all that uncommon a mistake,
and finding a file with the contents of the last module installed
is a baaad surprise at boot time..
PR: 26317
Submitted by: "T. William Wells" <bill@twwells.com> (the PR)
Gregory Bond <gnb@itga.com.au> (the actual patch)
Reviewed by: silence on -arch and -audit for the last 10 days
MFC after: 2 weeks
: 2001-07-18 Ruslan Ermilov <ru@FreeBSD.org>
:
: * tmac/groff_mdoc.man: Document new -width and -column syntax.
: Some other minor fixes.
: * tmac/an-old.tmac: Add `AT' and `UC' macros.
the components and trigger actions based on its position. This reduces
the need to remember the functions of various keys, and makes the
interface more consistant across library.
~
According to RFC 1112, which deals with multicasting, an application must
specify the interface on which it wished to send a multicast packet. In the
absence of such an interface, a default is selected.
Previous behavior in ip_output.c erroneously checked for a route to the
destination multicast address, rejecting the packet if none existed.
Applications got around this with a FAQ recommending a 224.0.0.0/29 route
to loopback. This worked because the multicast code in ip_output.c discards
route information if an interface was selected.
The previous commit skips the route check in the case where a multicast packet
is being send to an application-defined interface.
The only change in behavior, if no bugs were introduced, is the lack of
rejection of a multicast packet for which no route exists sent to an
application-defined interface.
MFC after: 2 weeks
for separating the startup scripts' list into individual filenames.
Run the shutdown scripts in reverse alphabetical order, so dependent
services are stopped before the services they depend upon.
Reviewed by: -arch, -audit
MFC after: 3 weeks
This macro was supposed to only match local IP addresses of
interfaces, and all consumers of this macro assume this as
well. (See IP_MULTICAST_IF and IP_ADD_MEMBERSHIP socket
options in the ip(4) manpage.)
This fixes a major security breach in IPFW-based firewalls
where the `me' keyword would match the other end of a P2P
link.
PR: kern/28567
for glue records and forces the glue record to be reloaded from the real NS.
The 5% ttl reduction can cause the glue IN A to timeout before the NS
record in certain situations, such as when the domain owner does not match
up NS records with the NIC. This behavior by domain owners is becoming
more common as primary zone serving iterates through another glue level
(i.e. exodus hosts the master NS's but the customer then redirects the
NS's to the real DNS servers). The result is that named would appear to
work properly for about 40 minutes, and then unexpectedly fail for that
zone. This causes named to behave very inconsistently and a google search
shows that it has obviously frustrated many, many people. So until the bind
guys make named behave consistently (either fail instantly or accomodate the
case), we need to set this option to accomodate the case. The result
will be much more consistent behavior and fewer head-scratching failures.
MFC after: 3 days
when we get an RX_ERR interrupt rather than the nge_rxeoc() handler. The
rxeoc (end of channel) handler attempts to reinitialize the whole NIC,
which we don't want to do if we only received a bad packet.
