ControlSockets are not created if tor starts with DisableNetwork set
The summary says it all basically, but note that if tor
was started with DisableNetwork 0
in torrc
so the control socket is opened, and then we set DisableNetwork 1
(in torrc
+ send a SIGHUP
), then the control socket is not closed. So there's also some inconsistency with this option being set at start vs setting it after start, which might help debugging this.
And just to be clear: ControlPort
TCP listeners work as expected vs DisableNetwork
, AFAICT.
FWIW, this affets the default torrc
(+ the default torrc
of course) in Debian with DisableNetwork 1
added.