Bug #9393

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

Added by intrigeri 2015-05-13 08:08:31 . Updated 2015-11-11 04:03:18 .

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

100%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:
269

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 Feature #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?

Subtasks

Related issues

Related to Tails - Feature #8262: Automatically test that all services have started correctly Resolved 2014-11-13

History

#1 Updated by intrigeri 2015-05-13 08:08:46

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

#2 Updated by intrigeri 2015-11-11 03:55:03

  • Status changed from Confirmed to In Progress

Applied in changeset commit:c195ff18add2ef18be45e133678b5895d8dce255.

#3 Updated by intrigeri 2015-11-11 04:03:18

  • 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
  • Deliverable for set to 269

#4 Updated by intrigeri 2015-11-11 04:03:40

  • blocks #8668 added