1. 10 Apr, 2012 7 commits
  2. 09 Apr, 2012 2 commits
  3. 08 Apr, 2012 5 commits
  4. 05 Apr, 2012 2 commits
    • Lennart Poettering's avatar
      systemd: add hardware watchdog support · e96d6be7
      Lennart Poettering authored
      This adds minimal hardware watchdog support to PID 1. The idea is that
      PID 1 supervises and watchdogs system services, while the hardware
      watchdog is used to supervise PID 1.
      
      This adds two hardware watchdog configuration options, for the runtime
      watchdog and for a shutdown watchdog. The former is active during normal
      operation, the latter only at reboots to ensure that if a clean reboot
      times out we reboot nonetheless.
      
      If the runtime watchdog is enabled PID 1 will automatically wake up at
      half the configured interval and write to the watchdog daemon.
      
      By default we enable the shutdown watchdog, but leave the runtime
      watchdog disabled in order not to break independent hardware watchdog
      daemons people might be using.
      
      This is only the most basic hookup. If necessary we can later on hook
      up the watchdog ping more closely with services deemed crucial.
      e96d6be7
    • Michal Schmidt's avatar
      job: use a lookup table for merging of job types · 348e27fe
      Michal Schmidt authored
      It is easier to see what job_type_merge() is doing when the merging
      rules are written in the form of a table.
      
      job_type_is_superset() contained redundant information. It can be
      simplified to a simple rule: Type A is a superset of B iff merging A
      with B gives A.
      
      Two job types are conflicting iff they are not mergeable.
      
      Make job_type_lookup_merge() the core function to decide the type
      merging. All other job_type_*() are just short wrappers around it.
      They can be inline.
      
      test-job-type gives the same results as before.
      btw, the systemd binary is smaller by almost 1 KB.
      348e27fe
  5. 04 Apr, 2012 7 commits
  6. 03 Apr, 2012 8 commits
  7. 02 Apr, 2012 5 commits
  8. 01 Apr, 2012 1 commit
  9. 30 Mar, 2012 1 commit
  10. 28 Mar, 2012 2 commits
    • Michal Schmidt's avatar
      bbd1a837
    • Michal Schmidt's avatar
      job: fix loss of ordering with restart jobs · dd17d388
      Michal Schmidt authored
      Suppose that foo.service/start is a job waiting on other job bar.service/start
      to finish. And then foo.service/restart is enqueued (not using
      --ignore-dependencies).
      
      Currently this makes foo.service start immediately, forgetting about the
      ordering to bar.service.
      
      The runnability check for JOB_RESTART jobs looks only at dependencies for
      stopping. That's actually correct, because restart jobs should be treated the
      same as stop jobs at first. The bug is that job_run_and_invalidate() does not
      treat them exactly the same as stop jobs. unit_start() gets called without
      checking for the runnability of the converted JOB_START job.
      
      The fix is to simplify the switch in job_run_and_invalidate(). Handle
      JOB_RESTART identically to JOB_STOP.
      Also simplify the handling of JOB_TRY_RESTART - just convert it to JOB_RESTART
      if the unit is active and let it fall through to the JOB_RESTART case.
      Similarly for JOB_RELOAD_OR_START - have a fall through to JOB_START.
      
      In job_finish_and_invalidate() it's not necessary to check for JOB_TRY_RESTART
      with JOB_DONE, because JOB_TRY_RESTART jobs will have been converted to
      JOB_RESTART already.
      
      Speeding up the restart of services in "auto-restart" state still works as
      before.
      
      Improves: https://bugzilla.redhat.com/show_bug.cgi?id=753586
      but it's still not perfect. With this fix the try-restart action will wait for
      the restart to complete in the right order, but the optimal behaviour would be
      to finish quickly (without disturbing the start job).
      dd17d388