bug#41791: [Shepherd] loses track of Tor

Hi Tobias, Tobias Geerinckx-Rice skribis: > ~ λ while :; do sudo herd restart tor; done > Service tor is not running. > Service tor has been started. > Service tor has been stopped. > Service tor could not be started. > Service tor is not running. > Service tor could not be started. > ^C > ~ λ p

bug#41791: [Shepherd] loses track of Tor

i'm not sure this is related, but it's certainly a bug in MAKE-KILL-DESTRUCTOR that it doesn't wait for the process to quit after sending it a signal, and thus may restart the service while the previous instance is still running. it's also not sending it a kill -9 after a timeout if the process is

bug#41791: [Shepherd] loses track of Tor

All, Unfortunately, this bug seems to have recropped up: . Kind regards, T G-R signature.asc Description: PGP signature

bug#41791: [Shepherd] loses track of Tor

Ludovic Courtès 写道： Oops, this one is fixed by b6b95685d0b478698d648f13afd927b1e1700d99. Impressive fanservice as always. The nginx issue may be different. The Shepherd 0.8.0 included fixes that should help for multi-process services like nginx. Let me know if it happens again. I will.

bug#41791: [Shepherd] loses track of Tor

Hi Tobias, Tobias Geerinckx-Rice skribis: > ~ λ while :; do sudo herd restart tor; done > Service tor is not running. > Service tor has been started. > Service tor has been stopped. > Service tor could not be started. > Service tor is not running. > Service tor could not be started. > ^C > ~ λ p

bug#41791: [Shepherd] loses track of Tor

All, --8<---cut here---start->8--- ~ λ while :; do sudo herd restart tor; done Service tor is not running. Service tor has been started. Service tor has been stopped. Service tor could not be started. Service tor is not running. Service tor could not be started