Hello Michael
On 2005-06-22 Michael Horn wrote:
> 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.
Sorry, bug after all it was you who requested that the daemon should be
upgraded. It's the way Unix and esp. Debian Linux works that when upgrading
a server, it is stopped, the new files are installed and then started.
Apache, MySQL, BIND, all work this way. And as a routing daemon like Quagga
normally does not run on "any" box but on a "router" I only expect somewhat
experienced admins as users.
Of course, just installing the new version but not restarting it might
be possible but IMHO is at least as dangerous as you might not know if
the next reboot happens to be on a crash during the night and expecting
to have a brand new version running perfectly might not be the savest thing
to do. It would be quite unexpected for normal Linux admins, too and major
work for me...
If on the other hand you planned the downtime anyway, just wait for it with
upgrading the package...
BTW, you exclude packages from normal "apt-get upgrade" runs with
echo "quagga hold" | dpkg --set-selections
it then just gets upgraded when you explicitly ask for it with
"apt-get install quagga".
bye,
-christian-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
