1. 27 Apr, 2014 1 commit
  2. 26 Apr, 2014 3 commits
  3. 09 Apr, 2013 1 commit
  4. 25 Mar, 2013 2 commits
    • Lennart Poettering's avatar
      units: introduce remote-fs-setup.target to pull in dependencies from remote mounts · e8d2f6cd
      Lennart Poettering authored
      This introduces remote-fs-setup.target independently of
      remote-fs-pre.target. The former is only for pulling things in, the
      latter only for ordering.
      
      The new semantics:
      
      remote-fs-setup.target: is pulled in automatically by all remote mounts.
      Shall be used to pull in other units that want to run when at least one
      remote mount is set up. Is not ordered against the actual mount units,
      in order to allow activation of its dependencies even 'a posteriori',
      i.e. when a mount is established outside of systemd and is only picked
      up by it.
      
      remote-fs-pre.target: needs to be pulled in automatically by the
      implementing service, is otherwise not part of the initial transaction.
      This is ordered before all remote mount units.
      
      A service that wants to be pulled in and run before all remote mounts
      should hence have:
      
      a) WantedBy=remote-fs-setup.target -- so that it is pulled in
      
      b) Wants=remote-fs-pre.target + Before=remote-fs-pre.target -- so that
         it is ordered before the mount point, normally.
      e8d2f6cd
    • Lennart Poettering's avatar
      Revert "remote-fs.target: want remote-fs-pre.target" · a69fe051
      Lennart Poettering authored
      This reverts commit 6bde0b32.
      
      We should not pull in remote-fs-pre.target unconditionally. It's
      supposed to be pulled in by the implementors of it, rather then its
      users.
      a69fe051
  5. 12 Mar, 2013 1 commit
    • Harald Hoyer's avatar
      remote-fs.target: want remote-fs-pre.target · 6bde0b32
      Harald Hoyer authored
      This pulls in remote-fs-pre.target if remote-fs.target is needed.
      
      Previously remote-fs-pre.target was not active, if no remote fs was
      mounted from /etc/fstab. So, every manual remote fs mount was ordered
      against the inactive remote-fs-pre.target and umount.target.
      
      Because remote-fs-pre.target was not active, the remote fs was umounted
      at umount.target time, which was too late (network already down).
      
      Now remote-fs-pre.target is active, even if no remote fs is mounted.
      On shutdown it is deactivated in the correct order and all manual remote
      fs mounts also.
      6bde0b32
  6. 21 May, 2012 1 commit
    • Lennart Poettering's avatar
      units: introduce new Documentation= field and make use of it everywhere · 49dbfa7b
      Lennart Poettering authored
      This should help making the boot process a bit easier to explore and
      understand for the administrator. The simple idea is that "systemctl
      status" now shows a link to documentation alongside the other status and
      decriptionary information of a service.
      
      This patch adds the necessary fields to all our shipped units if we have
      proper documentation for them.
      49dbfa7b
  7. 11 Apr, 2012 1 commit
    • Lennart Poettering's avatar
      relicense to LGPLv2.1 (with exceptions) · 5430f7f2
      Lennart Poettering authored
      We finally got the OK from all contributors with non-trivial commits to
      relicense systemd from GPL2+ to LGPL2.1+.
      
      Some udev bits continue to be GPL2+ for now, but we are looking into
      relicensing them too, to allow free copy/paste of all code within
      systemd.
      
      The bits that used to be MIT continue to be MIT.
      
      The big benefit of the relicensing is that closed source code may now
      link against libsystemd-login.so and friends.
      5430f7f2
  8. 28 Jul, 2011 2 commits
  9. 14 Jun, 2011 1 commit
    • Tom Gundersen's avatar
      remote-fs.target: do not order after network.target · 54763e12
      Tom Gundersen authored
      remote-fs.target is ordered after the {auto,}mount units. In case of automount
      we do not want to wait for the network to come up before proceeding. In case
      of a regular mount unit, the unit will be ordered after network.target
      so the behavior is unchanged.
      
      This speeds up boot quite a bit for me when having some services needing
      NetworkManager-wait-online.service, and having my home partition on nfs
      under an automountpoint.
      54763e12
  10. 13 Jul, 2010 1 commit
  11. 19 May, 2010 1 commit
  12. 16 May, 2010 3 commits