I have noticed that this behaviour changed. A few months ago we’ve implemented dynamic routing with bird4 and this problem didn’t exist, I was able to start/stop processes correctly.
Right now, after one of last updates, we have broken init script for bird4 - which in end effect also causes service to be not started after reboot:
# BIRD not running:
root@turris-bnd:~# ps ax | grep bird
12789 pts/0 S+ 0:00 grep bird
# Starting with init script fails silently: root@turris-bnd:~# /etc/init.d/bird4 start root@turris-bnd:~# ps ax | grep bird 12803 pts/0 S+ 0:00 grep bird # Starting process manually works fine root@turris-bnd:~# bird4 -c /etc/bird4.conf root@turris-bnd:~# ps ax | grep bird 12816 ? Ss 0:00 bird4 -c /etc/bird4.conf 12818 pts/0 S+ 0:00 grep bird
What should I do in order to restore functionality of the init script?
Marek Obuchowicz - KoreKontrol.eu