Hi, I second that bug and problem. Trying virtually anything I found out that strings like these: -s '/usr/sbin/service_quagga_start_%s' -k '/usr/sbin/service_quagga_stop_%s' do work flawless for watchquagga_options.
Also this line gets fully handed over to the watchquagga script: watchquagga_options=" -dz -R '/usr/sbin/service quagga restart' " and results in a good looking processlist: ps xa | grep -i quagga 6983 ? Ss 0:00 /usr/lib/quagga/zebra --daemon -A 127.0.0.1 6987 ? Ss 0:00 /usr/lib/quagga/ospfd --daemon -A 127.0.0.1 6991 ? Ss 0:00 /usr/lib/quagga/ospf6d --daemon -A ::1 6995 ? Ss 0:00 /usr/lib/quagga/watchquagga -dz -R '/usr/sbin/service quagga restart' zebra ospfd ospf6d But this doesn't work anyway (tested by kililng ospf6d, the down-state gets noted, but the restart fails). Then killed watchquagga and started is as root from a shell: /usr/lib/quagga/watchquagga -dz -R '/usr/sbin/service quagga restart' zebra ospfd ospf6d It promptly detects the not-running ospf6d and does a clean restart. After everything is back to normal (watchquagga has been started by the full restart by the init-script) I kill ospf6d again and this is it. State down gets detected, but the background restart command fails with error-code 2. I'd appreciate any hints from here on, we're now at the following solution: /etc/quagga/debian.conf -> watchquagga_enable=no And we start it separately in a script that does call itself if there is action to be done: /usr/lib/quagga/watchquagga -dz -R '/etc/init.d/quagga restart && /etc/rc.watchquagga' ospf6d ospfd zebra I'm feeling dumb, but that seems to be the only way to get in running on debian using the package quagga 0.99.21-4+wheezy1 best regards, Harald Kapper / kapper.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
