Bug#315467: Quagga explicitly flushes all routes when upgrading or restarting

2005-11-27 Thread Christian Hammers
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 th

Bug#315467: Quagga explicitly flushes all routes when upgrading or restarting

2005-11-27 Thread Matt Brown
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

Bug#315467: Quagga explicitly flushes all routes when upgrading or restarting

2005-11-27 Thread Christian Hammers
severity 315467 withlist tags 315467 + upstream thanks Hello Rens On 2005-11-24 Rens Houben wrote: > All of the quagga daemons can be instructed /not/ to flush their routes > upon exit; this is documented in their respective manpages (see the > --retain flag). > > What's causing the routes to t

Bug#315467: Quagga explicitly flushes all routes when upgrading or restarting

2005-11-24 Thread Rens Houben
I just ran into this bug, and read the e-mail discussion in the bts archive, and I find myself wondering if you actually understand the cause of the problem here at all... All of the quagga daemons can be instructed /not/ to flush their routes upon exit; this is documented in their respective man