1. 26 Jan, 2013 1 commit
  2. 19 Jan, 2013 3 commits
  3. 18 Jan, 2013 1 commit
  4. 17 Jan, 2013 1 commit
    • Nestor Ovroy's avatar
      core: corrects check of strduped controller string · 8755586e
      Nestor Ovroy authored
      In commit 246aa6dd (core: add bus API and systemctl commands for altering
      cgroup parameters during runtime), when rewriting unit_add_one_default_cgroup
      to prefered style, the check of strduped b->controller was incorrectly
      changed to check the containing structure. Correct it.
  5. 14 Jan, 2013 1 commit
  6. 10 Jan, 2013 1 commit
    • Lennart Poettering's avatar
      unit: allow extension of unit files with .d/*.conf drop-ins · 8afbb8e1
      Lennart Poettering authored
      For all unit files foobar.service we will now read
      foobar.service.d/*.conf, too. This may be used to override certain unit
      settings without having to edit unit files directly.
      This makes it really easy to change specific settings for services
      without having to edit any unit file:
      mkdir /etc/systemd/system/avahi-daemon.service.d/
      echo -e '[Service]\nNice=99' > /etc/systemd/system/avahi-daemon.service.d/nice.conf
      systemctl daemon-reload
  7. 23 Nov, 2012 1 commit
  8. 21 Nov, 2012 1 commit
  9. 18 Oct, 2012 1 commit
  10. 13 Oct, 2012 1 commit
  11. 18 Sep, 2012 4 commits
  12. 17 Sep, 2012 1 commit
  13. 13 Sep, 2012 1 commit
  14. 10 Sep, 2012 1 commit
  15. 04 Sep, 2012 2 commits
  16. 26 Jul, 2012 3 commits
    • Michal Schmidt's avatar
      unit: add missing deps in unit_dependency_table · ac6a4abe
      Michal Schmidt authored
      also reorder the table according to the enum order.
    • Michal Schmidt's avatar
    • Michal Sekletar's avatar
      systemd: added new dependency PartOf · 85e9a101
      Michal Sekletar authored
      This should address TODO item "new dependency type to "group" services
      in a target". Semantic of new dependency is as follows. Once configured
      it creates dependency which will cause that all dependent units get
      stopped if unit they all depend on is stopped or restarted.  Usual use
      case would be configuring PartOf=some.target in template unit file
      and WantedBy=some.target in [Install] section and enabling desired
      number of instances. In this case starting one instance won't pull in
      target but stopping or starting target(in case of WantedBy is properly
      configured) will cause stop/start of all instances.
  17. 19 Jul, 2012 2 commits
  18. 17 Jul, 2012 1 commit
  19. 16 Jul, 2012 3 commits
  20. 13 Jul, 2012 2 commits
  21. 10 Jul, 2012 2 commits
  22. 25 Jun, 2012 1 commit
  23. 13 Jun, 2012 1 commit
  24. 22 May, 2012 1 commit
  25. 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.
  26. 14 May, 2012 2 commits
    • Michal Schmidt's avatar
      unit: unit type dependent status messages · c6918296
      Michal Schmidt authored
      Instead of generic "Starting..." and "Started" messages for all unit use
      type-dependent messages. For example, mounts will announce "Mounting..."
      and "Mounted".
      Add status messages to units of types that used to be entirely silent
      (automounts, sockets, targets, devices). For unit types whose jobs are
      instantaneous, report only the job completion, not the starting event.
      Socket units with non-instantaneous jobs are rare (Exec*= is not used
      often in socket units), so I chose not to print the starting messages
      for them either.
      This will hopefully give people better understanding of the boot.
    • Michal Schmidt's avatar
      unit: print the color status marks on the left · 9ab7a8d2
      Michal Schmidt authored
      The alignment of the "[  OK  ]" and "[FAILED]" status marks to the right
      side of the terminal makes it difficult to link them with the messages
      on the left if your console is wide.
      I considered the options:
       1. Align them to the 80th column regardless of the console width.
          Disadvantage - either:
          - truncating messages needlessly, not using available space; or
          - If the message is long, write the mark over it. => ugly
       2. Write them to the 80th column for short messages,
          and further to the right for longer ones.
          - jagged look
       3. Write the marks on the left, before the message.
          - Breaks tradition from RHL.
          + slightly simpler code
          + Will annoy holy-traditionalists.
      I chose option 3.
      BTW, Debian now uses similar marks on the left with its makefile-style
      Special values of the "status" argument to status_vprintf are:
        NULL - no status mark, no message indentation
        ""   - no status mark, message indented as if the mark was there