Zbigniew Jędrzejewski-Szmek c4708f1323 tmpfiles: introduce the concept of unsafe operations ... Various operations done by systemd-tmpfiles may only be safely done at boot (e.g. removal of X lockfiles in /tmp, creation of /run/nologin). Other operations may be done at any point in time (e.g. setting the ownership on /{run,var}/log/journal). This distinction is largely orthogonal to the type of operation. A new switch --unsafe is added, and operations which should only be executed during bootup are marked with an exclamation mark in the configuration files. systemd-tmpfiles.service is modified to use this switch, and guards are added so it is hard to re-start it by mistake. If we install a new version of systemd, we actually want to enforce some changes to tmpfiles configuration immediately. This should now be possible to do safely, so distribution packages can be modified to execute the "safe" subset at package installation time. /run/nologin creation is split out into a separate service, to make it easy to override. https://bugzilla.redhat.com/show_bug.cgi?id=1043212 https://bugzilla.redhat.com/show_bug.cgi?id=1045849		2013-12-24 15:48:06 -05:00
..
legacy.conf	tmpfiles: introduce the concept of unsafe operations	2013-12-24 15:48:06 -05:00
Makefile	journal: add preliminary incomplete implementation	2011-10-07 22:02:05 +02:00
systemd-nologin.conf	tmpfiles: introduce the concept of unsafe operations	2013-12-24 15:48:06 -05:00
systemd.conf	tmpfiles: introduce the concept of unsafe operations	2013-12-24 15:48:06 -05:00
tmp.conf	namespace: include boot id in private tmp directories	2013-12-13 04:06:43 +01:00
x11.conf	tmpfiles: introduce the concept of unsafe operations	2013-12-24 15:48:06 -05:00