Improve systemd boot semantics of tails-wait-until-tor-has-bootstrapped.service
In the current state of feature/jessie, anything that wants to start
after graphical.target or multi-user.target won’t start unless the
network is up and Tor is configured correctly. Besides, as seen on
#8262 (closed), systemd won’t consider the system to have fully started unless
that’s the case. Is this what we want? Do we need to introduce another
target instead?
Related issues
- Related to #8262 (closed)
Original created by @intrigeri on 9393 (Redmine)