1. 20 Jul, 2019 1 commit
    • segfault's avatar
      Use BindsTo= and After= in tor-has-bootstrapped systemd units (refs: #16664) · d9ae8bf8
      segfault authored
      Currently, if tor@default.service stops for some reason (either stopped
      manually or unexpectedly), tails-tor-has-boostrapped.target is still
      active.
      
      Using BindsTo= in conjunction with After= ensures that the unit is
      always stopped if the other unit (tor@default.service) is stopped.
      See https://www.freedesktop.org/software/systemd/man/systemd.unit.html#BindsTo=
      
      This allows us to simplify config/chroot_local-includes/usr/local/sbin/tor-has-bootstrapped,
      which would only have to check if tails-tor-has-bootstrapped.target is active.
      Or, we could get rid of this script altogether, because instead of
      calling the script, applications can just run
      
          /bin/systemctl --quiet is-active tails-tor-has-bootstrapped.target
      
      themselves.
      d9ae8bf8
  2. 11 Jul, 2019 2 commits
  3. 11 Nov, 2015 1 commit
    • intrigeri's avatar
      Introduce a dedicated systemd target for "Tor has bootstrapped" state. · c195ff18
      intrigeri authored
      ... 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
      c195ff18