Hello Matt On 2005-11-28 Matt Brown wrote: > On Mon, 2005-11-28 at 00:54 +0100, Christian Hammers wrote: > > > Using the "--retain" option does not do what you want. It does, in so far > > you are indeed right, retain the routes when the Daemons are stopped but > > it DOES NOT import them when they are started again. The kernel continues > > to use them though. > <snip> > > So as far as I see it, the situation is still the same. There is no known > > unix routing suite that is able to get updated e.g. stopped and restarted > > without loosing the BGP/OSPF/etc routes and thus I can only ask the admin > > if he really likes to upgrade Quagga. I don't like this neither but please > > provide a working alternative that's better. > > I certainly I agree with your comments above Christian, but I have a > question. > > Why is the explcit flush needed in the init script? In my experience > zebra does a great job of removing any routes it has created from the > kernel's routing table on it's own.
But only if it is terminated correctly. When one of the daemons crash (which can happen e.g. if bgpd runs out of memory or just by chance) the routes stay stalled in the kernel routing table having the bad effect I described in the bug report. Most installations have some kind of watchdog script for this reason so the admin only sees "oh, bgpd crashed this night but restarted and is now working correctly so let's keep the box untouched" not knowing that he suddenly has maybe 120000 static routes that make this router a timebomb because you don't expect any other routes than those visible on the daemons consoles. > If this explicit flush was removed from the init script then it would be > much easier for the site admin to implement site specific policy for > things (such as --retain) that are not suitable for the Debian package. So far I can see no demand for another solution than the one as I guess that Rens was not aware of the implication that the --retain option has after the daemon is started again. bye, -christian- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
