Hello Christian,
On Wed, 22 Jun 2005, Christian Hammers wrote:
Hello Michael
On 2005-06-22 Michael Horn wrote:
updating quagga it removes all (163k) routes from the kernel without
prompting - this leads to extreme suffering in real-world scenarios.
Eh? How exactly do you expect a server to get upgraded without getting
restarted? Or do you just mean it should just not delete the routes
when stopping?
is should ask the user if it should. possibly one could employ a way to do
the update only on the next restart of the demon.
The latter is explained with the fact that Quagga cannot know from which
daemon a route has been inserted once it is there and would have severy
problems when starting up with all routes alredy present because even if
e.g. ospfd would be shutdown, it cannot safely decide if a given route
may now be killed if that route had already been present when Quagga had
been started.
yes - that's perfectly true.
You can normally assume that upgrading any Unix daemon means shutting it
down and afterwards restarting it again. Just like a Cisco router AFAIK
cannot be upgraded to a new IOS version while continuing to run.
cisco!=x86 quagga box ;)
after all - i just expect a software to warn me before it could cause
severe problems like a restarting quagga. so the best way to prevent users
from being scared to death would be if you warn them before you kill their
routing demon.
regards,
Michael
--
Michael Horn Network Consulting | nibbler.de | I route, therefore you are
--------------------------------+----------------------------------------
Po.Box 810221 | 90247 Nuremberg | GSM: +491777761111 | FAX: +491777762345
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
