Feature #10610

Consider using Type=oneshot for tails-upgrade-frontend.service and tails-security-check.service

Added by intrigeri 2015-11-23 07:43:15 . Updated 2015-11-30 03:04:47 .

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

100%

Feature Branch:
Type of work:
Research
Blueprint:

Starter:
Affected tool:
Deliverable for:
269

Description

This would allow us to order stuff after they’re done.

Subtasks

History

#1 Updated by intrigeri 2015-11-30 03:04:47

  • Status changed from Confirmed to Resolved
  • Assignee deleted (intrigeri)
  • % Done changed from 0 to 100

As commit:9fb0136 says:

> Also note that the units that may take ages to complete have Type=simple.
> With Type=oneshot, systemd would wait for them to complete before running any
> follow-up units, and before considering the target they’re part of has been
> reached. Two of our units can take minutes to complete, so the desktop.target
> startup would fail. Now, using Type=simple has one drawback: it makes it harder
> to order other units relatively to tails-security-check-wrapper’s and
> tails-upgrade-frontend-wrapper’s completion. This doesn’t feel too bothering,
> though: it’s more likely that we want to configure these units to start after
> others, than the opposite.