Open adrelanos opened 8 years ago
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 After=tor@default.service 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
Okay, great.
I don't know how severe that issue is.
Perhaps in corridor-data.service should use
After=tor.service
?I am not sure
After=tor@default.service
is also required.Generally, could you look into
sudo journalctl -b
please to see if the boot order looks right?