cvs commit: src/sys/net rtsock.c

[Peter Grehan]

> A rtmessage should never ever be dropped.  That would wedge the synchronized
> state of any userland routing daemons.

  That only works with infinite memory or if you can flow-control
the sources of the messages. A drop is easy to cause e.g. by
downing a SONET link that might have many layers of serial ifnets
muxed on top of it. Gated used to handle this by looking for a gap
in sequence number and then falling back to a sysctl to re-read the
routing table/interface list. Hopefully not frequent events !

  Ask the Juniper guys how they handle this case :-)

later,

Peter.