start corridor-data.service after tor.service

[adrelanos]

Jul 31 21:20:27 sys-corridor corridor-data[731]: /usr/sbin/corridor-data: 39: /usr/sbin/corridor-data: cannot open /var/run/tor/control.authcookie: No such file
Jul 31 21:20:27 sys-corridor corridor-data[731]: 2016/07/31 21:20:27 socat[815] E connect(5, AF=1 "/var/run/tor/control", 22): No such file or directory

I don't know how severe that issue is.

Perhaps in corridor-data.service should use After=tor.service?

I am not sure [email protected] is also required.

Generally, could you look into sudo journalctl -b please to see if the boot order looks right?

[rustybird]

I don't know how severe that issue is.

That's just corridor-data trying to connect and authenticate to the control port once per second, all working as expected.

Perhaps in corridor-data.service should use After=tor.service?

I am not sure [email protected] is also required.

corridor-data does not necessarily have any relation to the tor daemon running on localhost (it could be using bridges or a tor daemon on another computer). Adding the ordering to remove some noise from the journal in most setups sounds reasonable nevertheless, but I have to check if this would introduce any cycles.

Generally, could you look into sudo journalctl -b please to see if the boot order looks right?

It does on my systems

[adrelanos]

Okay, great.