Project

General

Profile

Bug #9393

Improve systemd boot semantics of tails-wait-until-tor-has-bootstrapped.service

Added by intrigeri over 3 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
05/13/2015
Due date:
% Done:

100%

QA Check:
Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Affected tool:

Description

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, 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 Tails - Feature #8262: Automatically test that all services have started correctly Resolved 11/13/2014

Associated revisions

Revision c195ff18 (diff)
Added by intrigeri almost 3 years ago

Introduce a dedicated systemd target for "Tor has bootstrapped" state.

... and move tails-wait-until-tor-has-bootstrapped.service from
default.target to it. The main effect is that anything that wants to
start after graphical.target or multi-user.target does not have to wait
for Tor to have bootstrapped (which could very well never happen, e.g.
when working offline) anymore.

Will-fix: #9393

History

#1 Updated by intrigeri over 3 years ago

  • Related to Feature #8262: Automatically test that all services have started correctly added

#2 Updated by intrigeri almost 3 years ago

  • Status changed from Confirmed to In Progress

#3 Updated by intrigeri almost 3 years ago

  • Subject changed from Check systemd boot semantics of tails-wait-until-tor-has-bootstrapped.service to Improve systemd boot semantics of tails-wait-until-tor-has-bootstrapped.service
  • Status changed from In Progress to Resolved
  • Assignee deleted (intrigeri)
  • % Done changed from 0 to 100
  • Type of work changed from Research to Code

Also available in: Atom PDF