this basically logjammed on this issue. Either procd needed to be modified to
be able to
send an arbitrary signal, or babel changed to take sighup as a reload.
Or using an indirection: script for procd systems which launch Babel and
capture sighups… :p
(well, at least it keeps Babel safe!)
On Tue, Mar 17, 2015 at 01:36:13PM +0100, Henning Rogge wrote:
On Tue, Mar 17, 2015 at 1:13 PM, Gabriel Kerneis gabr...@kerneis.info wrote:
Le 2015-03-17 12:45, Juliusz Chroboczek a écrit :
2) got the new vars into openwrt, or shall I do?
Gabriel?
Which vars are we talking about? I
On 17 March 2015 15:50:41 CET, Baptiste Jonglez bapti...@bitsofnetworks.org
wrote:
On Tue, Mar 17, 2015 at 01:36:13PM +0100, Henning Rogge wrote:
On Tue, Mar 17, 2015 at 1:13 PM, Gabriel Kerneis
gabr...@kerneis.info wrote:
Le 2015-03-17 12:45, Juliusz Chroboczek a écrit :
2) got the new vars
On Tue, Mar 17, 2015 at 1:13 PM, Gabriel Kerneis gabr...@kerneis.info wrote:
Le 2015-03-17 12:45, Juliusz Chroboczek a écrit :
2) got the new vars into openwrt, or shall I do?
Gabriel?
Which vars are we talking about? I believe I added new ones whenever
necessary on each release (so
Le 2015-03-17 12:45, Juliusz Chroboczek a écrit :
1) Did the issue with procd ever get resolved? (sighup I think it
was)
Gabriel, Steven? Can procd be configured not to send SIGHUP, or
shall
I add an option to babeld to ignore it? (Currently babeld terminates
on
SIGHUP, and I like it that
1) Did the issue with procd ever get resolved? (sighup I think it was)
Gabriel, Steven? Can procd be configured not to send SIGHUP, or shall
I add an option to babeld to ignore it? (Currently babeld terminates on
SIGHUP, and I like it that way, since it prevents a babeld from sticking
around
My quest is always for an extra 9 of reliability. Anyplace where you can
make something more robust (even if it is out at the .99) level, I
tend to like to do in order to have the highest MTBF possible in
combination with all the other moving parts on the spacecraft (spaceship
earth).
One
7 matches
Mail list logo