[tor-dev] No Control Socket when DisableNetwork 1

[Roger Dingledine]

On Fri, Jan 19, 2018 at 11:22:00PM +0000, iry wrote:
> However, it seems when DisableNetwork is set to 1,
> /var/run/tor/control does not exist anymore making us cannot get a
> controller from socket file.
>[...]
> I searched on Tor-trac but did not find any similar report. Therefore,
> would you please tell me wether Tor intentionally behaves like this or
> this is a bug? (If this is a bug, I can definitely help to report it
> to Tor-trac.)

Yeah, I think this is supposed to work. In fact, I agree with Yawning
in that I think it *does* work.

My first suggestion would be to see if your Tor process actually
successfully started in the "DisableNetwork 1" case. Maybe it didn't
actually start up? Maybe the logs give you some hints?

My second suggestion would be to get a Tor binary and run it yourself,
not as part of a package. If it works there, then you know that your
next steps are to figure out why your package isn't working for you.

If you can get a minimal case reproducing the bug without a package,
systemd, etc, in the picture, that's a great time to file a trac ticket.

Thanks!
--Roger