Commit 3cdb6d5a authored by segfault's avatar segfault

Remove obsolete manual stops of tails-tor-has-bootstrapped.target (refs: #16664)

tor@default.service is stopped above the removed lines, which now
automatically stops tails-tor-has-bootstrapped.target.
parent 7f7757cd
......@@ -30,10 +30,6 @@ systemctl stop tor@default.service
# tordate/20-time.sh), so deleting it seems like a Good Thing(TM).
rm -f "${TOR_LOG}"
# Let the rest of the system know that Tor is not working at the moment.
# This matters e.g. if we have already bootstrapped.
systemctl --no-block restart tails-tor-has-bootstrapped.target
# The Tor syscall sandbox is not compatible with managed proxies.
# We could possibly detect whether the user has configured any such
# thing via Tor Launcher later (e.g. in 60-tor-ready.sh),
......
......@@ -33,7 +33,6 @@ def post_snapshot_restore_hook
if $vm.has_network?
if $vm.execute("systemctl --quiet is-active tor@default.service").success?
$vm.execute("systemctl stop tor@default.service")
$vm.execute("systemctl --no-block restart tails-tor-has-bootstrapped.target")
$vm.host_to_guest_time_sync
$vm.execute("systemctl start tor@default.service")
wait_until_tor_is_working
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment