On Tue, 12 Apr 2016, Rian Hunter wrote:
> There's nothing in my journal or /var/log/tor/log* to indicate any failure.
>
> But I tested just now with a bogus bind address and tor fails to start.
> Nothing in the log except "Interrupt: exiting cleanly" though journalctl
> shows it failed to start (without reason).
>
> I think your guess is correct. Maybe tor.service should wait on Debian ifup
> -a (or equivalent)?
I think it's supposed to, but maybe network.target should be replaced by
after network-online.target.
If tor does not start on system-boot reproducible, can you add it to the
unit file?
mkdir /etc/systemd/system/tor@default.service.d/
cat > /etc/systemd/system/tor@default.service.d/override.conf << EOF
[Unit]
Wants=network-online.target
After=network.target network-online.target nss-lookup.target
EOF
should do it for testing purposes.
Cheers,
--
| .''`. ** Debian **
Peter Palfrader | : :' : The universal
https://www.palfrader.org/ | `. `' Operating System
| `- https://www.debian.org/
