Bug#315467: missing kill-quagga-prompt when upgrading
Please have a look at how openvpn is upgraded. people like you are the source of instability in the global routing table. Have a nice day. regards Michael Horn ...who switched to lfs or openbgpd instead of debian. p.s. you might want to read up a bit on how the world out there works before building crappy packets and annoying other people with 'em. -- Michael Horn Network Consulting | nibbler.de | I route, therefore you are + Po.Box 810221 | 90247 Nuremberg | GSM: +4916 | FAX: +49162345 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#315467: missing kill-quagga-prompt when upgrading
Package: quagga Version: 0.98.3-1 Severity: grave Justification: causes non-serious data loss updating quagga it removes all (163k) routes from the kernel without prompting - this leads to extreme suffering in real-world scenarios. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages quagga depends on: ii debconf 1.4.30.13Debian configuration management sy ii iproute 20041019-3 Professional tools to control the ii libc6 2.3.2.ds1-21 GNU C Library: Shared libraries an ii libcap1 1:1.10-14support for getting/setting POSIX. ii libncurses5 5.4-4Shared libraries for terminal hand ii libpam0g0.76-22 Pluggable Authentication Modules l ii libreadline44.3-11 GNU readline and history libraries ii libsnmp55.1.2-6.1NET SNMP (Simple Network Managemen ii libssl0.9.7 0.9.7e-3 SSL shared libraries ii logrotate 3.7-2Log rotation utility -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#315467: missing kill-quagga-prompt when upgrading
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: +4916 | FAX: +49162345 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
