We are using bird als a routing daemon in a meshed ethernet fabric. Bird runs 
on the connected hosts as well as on the network equipment to archive full 
layer 3 connectivity.

When we upgrade the installed packages on the Hosts, the upgrade process stops 
bird, does upgrades and starts bird again.

These behavior lead to a loss of connectivity for one up to several minutes, 
which make the upgrade process very disruptive.

Usually, i would expect an upgrade and a restart of the daemon after the 
upgrade, which would keep the time in which the host is offline rather short.

Following questions arise:

* is this behavior intended, or is it a unintended side effect?
* did you consider this type of setups, when you implemented the upgrade 
process this disruptive?
* Can you consider to fix it, easing the upgrade process in this type of setups?

In our careful evaluation, we think, using the -R parameter of dh_installinit 
could ease our suffering, resulting in following patch:

diff -ruN bird-1.6.2.old/debian/rules bird-1.6.2/debian/rules
--- bird-1.6.2.old/debian/rules 2016-09-29 20:49:00.000000000 +0200
+++ bird-1.6.2/debian/rules     2016-10-11 10:27:00.717429976 +0200
@@ -69,8 +69,8 @@
        dh_strip -O--dbgsym-migration='bird-dbg (<< 1.6.0-2~), bird-bgp-dbg (<< 

-       dh_installinit --name=bird
-       dh_installinit --name=bird6
+       dh_installinit --name=bird -R
+       dh_installinit --name=bird6 -R

DB2MAN = /usr/share/sgml/docbook/stylesheet/xsl/nwalsh/manpages/docbook.xsl
XP     = xsltproc -''-nonet -''-param man.charmap.use.subset "0"

Regards, Alexander Morlang


SysEleven GmbH
Ohlauer Straße 43
10999 Berlin

T +49 30 233 2012 0
F +49 30 616 7555 0


Aktueller System-Status immer unter:

Firmensitz: Berlin
Registergericht: AG Berlin Charlottenburg, HRB 108571 B
Geschäftsführer: Marc Korthaus, Jens Ihlenfeld

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Reply via email to