1. 06 May, 2013 1 commit
  2. 25 Apr, 2013 2 commits
    • Harald Hoyer's avatar
      systemd: record the timestamps as early as possible · c3a170f3
      Harald Hoyer authored
      The time for systemd initialization and selinux policy loading
      is accounted to the initrd or the kernel, which is wrong.
      Instead of:
      Startup finished in 5.559s (firmware) + 36ms (loader) + 665ms (kernel) +
      975ms (initrd) + 1.410s (userspace) = 8.647s
      the more correct output is:
      Startup finished in 5.559s (firmware) + 36ms (loader) + 665ms (kernel) +
      475ms (initrd) + 1.910s (userspace) = 8.647s
    • Lennart Poettering's avatar
      conf-parser: restrict .include usage · db5c0122
      Lennart Poettering authored
      Disallow recursive .include, and make it unavailable in anything but
      unit files.
  3. 24 Apr, 2013 1 commit
  4. 23 Apr, 2013 1 commit
  5. 18 Apr, 2013 2 commits
  6. 17 Apr, 2013 3 commits
  7. 08 Apr, 2013 1 commit
    • Harald Hoyer's avatar
      Do not serialize environment, when switching root · b3680f49
      Harald Hoyer authored
      When switching root, i.e. LANG can be set to the locale of the initramfs
      or "C", if it was unset. When systemd deserializes LANG in the real root
      this would overwrite the setting previously gathered by locale_set().
      To reproduce, boot with an initramfs without locale.conf or change
      /etc/locale.conf to a different language than the initramfs and check a
      daemon started by systemd:
      $ tr "$\000" '\n' </proc/$(pidof sshd)/environ | grep LANG
      To prevent that, serialization of environment variables is skipped, when
      serializing for switching root.
  8. 06 Apr, 2013 1 commit
  9. 05 Apr, 2013 1 commit
    • Zbigniew Jędrzejewski-Szmek's avatar
      Use initalization instead of explicit zeroing · b92bea5d
      Zbigniew Jędrzejewski-Szmek authored
      Before, we would initialize many fields twice: first
      by filling the structure with zeros, and then a second
      time with the real values. We can let the compiler do
      the job for us, avoiding one copy.
      A downside of this patch is that text gets slightly
      bigger. This is because all zero() calls are effectively
      $ size build/.libs/systemd
               text    data     bss     dec     hex filename
      before 897737  107300    2560 1007597   f5fed build/.libs/systemd
      after  897873  107300    2560 1007733   f6075 build/.libs/systemd
      … actually less than 1‰.
      A few asserts that the parameter is not null had to be removed. I
      don't think this changes much, because first, it is quite unlikely
      for the assert to fail, and second, an immediate SEGV is almost as
      good as an assert.
  10. 04 Apr, 2013 1 commit
    • Lennart Poettering's avatar
      util: make time formatting a bit smarter · 2fa4092c
      Lennart Poettering authored
      Instead of outputting "5h 55s 50ms 3us" we'll now output "5h
      55.050003s". Also, while outputting the accuracy is configurable.
      Basically we now try use "dot notation" for all time values > 1min. For
      >= 1s we use 's' as unit, otherwise for >= 1ms we use 'ms' as unit, and
      finally 'us'.
      This should give reasonably values in most cases.
  11. 03 Apr, 2013 1 commit
  12. 31 Mar, 2013 2 commits
  13. 22 Mar, 2013 3 commits
  14. 14 Mar, 2013 1 commit
  15. 07 Mar, 2013 4 commits
  16. 06 Mar, 2013 1 commit
    • Tom Gundersen's avatar
      main: ISOLATE rather than REPLACE default.target · 95f1b47d
      Tom Gundersen authored
      This allows switch-root to work correctly if a unit is active both before and
      after the switch-root, but its dependencies change. Before the patch, any
      dependencies added to active units by switch-root will not be pulled, in
      particular filesystems configured in /etc/fstab would not be activated if
      local-fs.target was active in the initrd.
      It is not clear to me if there is a bug in the REPLACE handling, or if it is
      working as expected and that we really want to use ISOLATE instead as this patch
  17. 14 Feb, 2013 1 commit
  18. 11 Feb, 2013 1 commit
  19. 04 Jan, 2013 1 commit
  20. 22 Dec, 2012 1 commit
  21. 20 Nov, 2012 1 commit
  22. 27 Oct, 2012 1 commit
  23. 16 Oct, 2012 1 commit
  24. 24 Sep, 2012 1 commit
  25. 18 Sep, 2012 1 commit
    • Zbigniew Jędrzejewski-Szmek's avatar
      core: move ManagerRunningAs to shared · 67445f4e
      Zbigniew Jędrzejewski-Szmek authored
      Note: I did s/MANAGER/SYSTEMD/ everywhere, even though it makes the
      patch quite verbose. Nevertheless, keeping MANAGER prefix in some
      places, and SYSTEMD prefix in others would just lead to confusion down
      the road. Better to rip off the band-aid now.
  26. 17 Sep, 2012 3 commits
    • Lennart Poettering's avatar
      main: when transitioning from initrd to the main system log to kmsg · a866073d
      Lennart Poettering authored
      When the new PID is invoked the journal socket from the initrd might
      still be around. Due to the default log target being journal we'd log to
      that initially when the new main systemd initializes even if the kernel
      command line included a directive to redirect systemd's logging
      With this fix we initially always log to kmsg now, if we are PID1, and
      only after parsing the kernel cmdline try to open the journal if that's
      (The effective benefit of this is that SELinux performance data is now
      logged again to kmsg like it used to be.)
    • Kay Sievers's avatar
      hwclock: always set the kernel's timezone · 72edcff5
      Kay Sievers authored
      Properly tell the kernel at bootup, and any later time zone changes,
      the actual system time zone.
      Things like the kernel's FAT filesystem driver needs the actual time
      zone to calculate the proper local time to use for the on-disk time
    • Lennart Poettering's avatar
      main: bump up RLIMIT_NOFILE for systemd itself · 4096d6f5
      Lennart Poettering authored
      For setups with many listening sockets the default kernel resource limit
      of 1024 fds is not enough. Bump this up to 64K to avoid any limitations
      in this regard. We are careful to pass on the kernel default to daemons
      however, since normally resource limits are a good to enforce,
      especially since select() can't handle fds > 1023.
  27. 10 Sep, 2012 1 commit
  28. 07 Sep, 2012 1 commit