1. 22 Jun, 2012 2 commits
  2. 21 Jun, 2012 3 commits
    • Lennart Poettering's avatar
    • Lennart Poettering's avatar
      readahead: merge three binaries into one · 87ce22cc
      Lennart Poettering authored
      since the binaries share much of the same code and we better load only
      one binary instead of two from disk at early boot let's merge the three
      readahead binaries into one. This also allows us to drop a lot of
      duplicated code.
      87ce22cc
    • Lennart Poettering's avatar
      rpm: include RPM macro definition for .spec snippets · 590f18a2
      Lennart Poettering authored
      Let's try to standardize a bit the RPM macros used for
      installing/uninstalling services.
      
      This only covers the non-SysV compat bits, since that tends to vary
      widely between the various distros.
      
      Usage:
      
      Add %{?systemd_requires} to the header of the spec file. And then:
      
      %post
      %systemd_post foobar.service
      
      %preun
      %systemd_preun foobar.service
      
      %postun
      %systemd_postun foobar.service
      
      And, instead of the latter, in case the service shall be restarted on updates:
      
      %postun
      %systemd_postun_restart foobar.service
      590f18a2
  3. 18 Jun, 2012 1 commit
  4. 10 Jun, 2012 1 commit
    • Kay Sievers's avatar
      udev: always use $(rootprefix)/lib/udev for libexecdir · 8e8eb8fb
      Kay Sievers authored
      On Sat, Jun 9, 2012 at 12:46 AM, Malte Starostik <lists@malte.homeip.net> wrote:
      > From: Malte Starostik <m-starostik@versanet.de>
      >
      > Rules get installed in $(libexecdir)/udev/, so are keymaps.  Helper
      > binaries go to $(rootprefix)/lib/udev though.  Problem is, in the code,
      > both are referenced via UDEVLIBEXECDIR which is defined to the former
      > location.  Result: systemd-udev can't find e.g. the keymap binary to
      > apply keymaps.
      8e8eb8fb
  5. 07 Jun, 2012 2 commits
  6. 05 Jun, 2012 1 commit
    • Auke Kok's avatar
      readahead: Add tool to analyze the contents of the pack file. v3. · cae544bc
      Auke Kok authored
      This patch adds code to compile 'systemd-readahead-analyze' and install
      it into $bindir.
      
      Use this program to parse the contents of the readahead pack file, or
      an arbitrary pack file and display which files are listed in it, and
      how much of the files are requested to be readahead.
      
      This code is not new - it's partially taken from sreadahead (formerly
      maintained by Arjan van der Ven and me, and was originally written
      by me), and adapted with the right bits to parse the systemd
      readahead pack files, which are slightly different in format.
      
      v2 adds a common READAHEAD_PACK_FILE_VERSION used in all the code
      to provide a quick way to assure all these programs are always
      synchronized. v3 fixes the integer math.
      cae544bc
  7. 04 Jun, 2012 1 commit
  8. 02 Jun, 2012 1 commit
  9. 01 Jun, 2012 3 commits
  10. 31 May, 2012 2 commits
  11. 30 May, 2012 4 commits
  12. 24 May, 2012 1 commit
  13. 23 May, 2012 1 commit
  14. 22 May, 2012 3 commits
  15. 21 May, 2012 1 commit
  16. 16 May, 2012 1 commit
  17. 15 May, 2012 2 commits
  18. 08 May, 2012 2 commits
  19. 07 May, 2012 2 commits
  20. 04 May, 2012 1 commit
  21. 03 May, 2012 1 commit
  22. 30 Apr, 2012 1 commit
  23. 25 Apr, 2012 2 commits
    • Michal Schmidt's avatar
      core: add NOP jobs, job type collapsing · e0209d83
      Michal Schmidt authored
      Two of our current job types are special:
      JOB_TRY_RESTART, JOB_RELOAD_OR_START.
      
      They differ from other job types by being sensitive to the unit active state.
      They perform some action when the unit is active and some other action
      otherwise. This raises a question: when exactly should the unit state be
      checked to make the decision?
      
      Currently the unit state is checked when the job becomes runnable. It's more
      sensible to check the state immediately when the job is added by the user.
      When the user types "systemctl try-restart foo.service", he really intends
      to restart the service if it's running right now. If it isn't running right
      now, the restart is pointless.
      
      Consider the example (from Bugzilla[1]):
      
      sleep.service takes some time to start.
      hello.service has After=sleep.service.
      Both services get started. Two jobs will appear:
       hello.service/start  waiting
       sleep.service/start  running
      Then someone runs "systemctl try-restart hello.service".
      
      Currently the try-restart operation will block and wait for
      sleep.service/start to complete.
      
      The correct result is to complete the try-restart operation immediately
      with success, because hello.service is not running. The two original
      jobs must not be disturbed by this.
      
      To fix this we introduce two new concepts:
      - a new job type: JOB_NOP
        A JOB_NOP job does not do anything to the unit. It does not pull in any
        dependencies. It is always immediately runnable. When installed to a unit,
        it sits in a special slot (u->nop_job) where it never conflicts with
        the installed job (u->job) of a different type. It never merges with jobs
        of other types, but it can merge into an already installed JOB_NOP job.
      
      - "collapsing" of job types
        When a job of one of the two special types is added, the state of the unit
        is checked immediately and the job type changes:
        JOB_TRY_RESTART     -> JOB_RESTART or JOB_NOP
        JOB_RELOAD_OR_START -> JOB_RELOAD or JOB_START
        Should a job type JOB_RELOAD_OR_START appear later during job merging, it
        collapses immediately afterwards.
        Collapsing actually makes some things simpler, because there are now fewer
        job types that are allowed in the transaction.
      
      [1] Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=753586
      e0209d83
    • Lennart Poettering's avatar
      timedated: introduce systemd-timedated-ntp.target which is controlled by timedated's NTP setting · e2875c46
      Lennart Poettering authored
      We shouldn't hardcode the name of the NTP implementation in the
      timedated mechanism, especially since Fedora currently switched from NTP
      to chrony.
      
      This patch introduces a new target that is enabled/disabled instead of
      the actual NTP implementation. The various NTP implementations should
      then add .wants/ symlinks to their services and BindTo back to the
      target, so that their implementations are started/stopped jointly with
      the target.
      
      https://bugzilla.redhat.com/show_bug.cgi?id=815748
      e2875c46
  24. 24 Apr, 2012 1 commit