summaryrefslogtreecommitdiff
path: root/src/shared/utmp-wtmp.h
diff options
context:
space:
mode:
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2013-12-20 20:25:39 -0500
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2013-12-24 15:48:06 -0500
commitc4708f132381e4bbc864d5241381b5cde4f54878 (patch)
tree1802c55a1aa92e3855748a0e6463ee6020f0286c /src/shared/utmp-wtmp.h
parentef72c1f06e2bc696a799cd31a1e0ed25cc999ea4 (diff)
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
Diffstat (limited to 'src/shared/utmp-wtmp.h')
0 files changed, 0 insertions, 0 deletions