David Herrmann f9e4283df3 login: simply XDG_RUNTIME_DIR management
Lets not pretend we support changing XDG_RUNTIME_DIR via logind state
files. There is no reason to ever write the string into /run, as we
allocate it statically based on the UID, anyway. Lets stop that and just
allocate the runtime_path in "struct User" at all times.

We keep writing it into the /run state to make sure pam_systemd of
previous installs can still read it. However, pam_systemd is now fixed to
allocate it statically as well, so we can safely remove that some time in
the future.

Last but not least: If software depends on systemd, they're more than free
to assume /run/user/$uid is their runtime dir. Lets not require sane
applications to query the environment to get their runtime dir. As long as
applications know their login-UID, they should be safe to deduce the
runtime dir.
2015-11-16 15:34:36 +01:00
2015-07-06 17:47:38 +02:00
2015-11-14 09:54:17 +01:00
2015-11-10 19:33:06 -05:00
2015-11-16 03:15:10 +00:00
2015-07-27 20:15:34 +02:00
2015-08-31 18:12:37 +02:00
2015-11-15 20:36:22 +01:00
2015-06-03 00:22:53 +02:00
2014-06-04 15:41:10 -04:00
2015-07-27 20:15:34 +02:00
2015-11-10 19:33:06 -05:00
2015-11-14 09:54:17 +01:00
2015-11-15 17:30:33 +01:00
2015-11-02 10:05:20 -06:00
2015-11-16 15:05:00 +01:00

systemd - System and Service Manager

Build Status
Coverity Scan Status

Details

  • General information about systemd can be found in the systemd Wiki
  • Information about build requirements are provided in the README file
S
Description
systemd patched fork
Readme
409 MiB
Languages
C 88.5%
Shell 5.7%
Python 4.6%
Meson 1.1%