shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-11-05 06:52:22 +03:00
Code
d08191a242
systemd/tmpfiles.d/systemd.conf.m4

58 lines
2.1 KiB
Plaintext
Raw Normal View History

tmpfiles: install default tmpfiles configuration
2010-09-29 00:32:53 +04:00
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
relicense to LGPLv2.1 (with exceptions) We finally got the OK from all contributors with non-trivial commits to relicense systemd from GPL2+ to LGPL2.1+. Some udev bits continue to be GPL2+ for now, but we are looking into relicensing them too, to allow free copy/paste of all code within systemd. The bits that used to be MIT continue to be MIT. The big benefit of the relicensing is that closed source code may now link against libsystemd-login.so and friends.
2012-04-12 02:20:58 +04:00
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
tmpfiles: install default tmpfiles configuration
2010-09-29 00:32:53 +04:00
# (at your option) any later version.
tmpfiles: include reference to man page in tmpfiles files
2010-11-11 01:58:01 +03:00
# See tmpfiles.d(5) for details
tmpfiles: don't do automatic cleanup in $XDG_RUNTIME_DIR Now that logind will clean up all IPC resources of a user we should really consider $XDG_RUNTIME_DIR as just another kind of IPC with the same life-cycle logic as the other IPC resources. This should be safe now to do since every user gets his own $XDG_RUNTIME_DIR tmpfs instance with a fixed size limit, so that flooding of it will more effectively be averted.
2014-06-30 21:06:18 +04:00
d /run/user 0755 root root -
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-21 05:25:39 +04:00
F! /run/utmp 0664 root utmp -
tmpfiles: enforce new /var/lock semantics http://lists.freedesktop.org/archives/systemd-devel/2011-March/001823.html
2011-04-01 02:43:28 +04:00
path: optionally, create watched directories in .path units
2011-04-10 03:30:14 +04:00
d /run/systemd/ask-password 0755 root root -
sd-login: beef up login api, to add monitoring and enumerating
2011-07-22 23:01:15 +04:00
d /run/systemd/seats 0755 root root -
d /run/systemd/sessions 0755 root root -
d /run/systemd/users 0755 root root -
machined: split out machine registration stuff from logind Embedded folks don't need the machine registration stuff, hence it's nice to make this optional. Also, I'd expect that machinectl will grow additional commands quickly, for example to join existing containers and suchlike, hence it's better keeping that separate from loginctl.
2013-07-02 05:47:23 +04:00
d /run/systemd/machines 0755 root root -
shutdownd: rework interface, allow subscribing to scheduled shutdowns This extends the shutdownd interface to expose schedule shutdown information in /run/systemd/shutdown/schedule. This also cleans up the shutdownd protocol and documents it in a header file sd-shutdown.h. This is supposed to be used by client code that wants to control and monitor scheduled shutdown.
2012-04-11 04:04:46 +04:00
d /run/systemd/shutdown 0755 root root -
build-sys: configure the list of system users, files and directories Choose which system users defined in sysusers.d/systemd.conf and files or directories in tmpfiles.d/systemd.conf, should be provided depending on comile-time configuration.
2014-11-28 17:59:59 +03:00
m4_ifdef(`ENABLE_NETWORKD',
networkd: split runtime config dir from state dir Configuration will be in root:root /run/systemd/network and state will be in systemd-network:systemd-network /run/systemd/netif This matches what we do for logind's seat/session state.
2014-06-03 20:57:47 +04:00
d /run/systemd/netif 0755 systemd-network systemd-network -
d /run/systemd/netif/links 0755 systemd-network systemd-network -
d /run/systemd/netif/leases 0755 systemd-network systemd-network -
build-sys: configure the list of system users, files and directories Choose which system users defined in sysusers.d/systemd.conf and files or directories in tmpfiles.d/systemd.conf, should be provided depending on comile-time configuration.
2014-11-28 17:59:59 +03:00
)m4_dnl
tmpfiles: write /run/nologin during early boot to disallow too early user logins systemd-user-sessoins.service will later on remove the flag file, thus permitting user logins when the time has come.
2012-06-25 19:35:13 +04:00
tmpfiles: explicitly set mode for /run/log
2014-06-30 21:53:10 +04:00
d /run/log 0755 root root -
tmpfiles: get rid of "m" lines, make them redundant by "z" "m" so far has been a non-globbing version of "z". Since this makes it quite redundant, let's get rid of it. Remove "m" from the man pages, beef up "z" docs instead, and make "m" nothing more than a compatibility alias for "z".
2014-06-11 01:42:16 +04:00
z /run/log/journal 2755 root systemd-journal - -
tmpfiles: don't allow read access to journal files to users not in systemd-journal Also, don't apply access mode recursively to /var/log/journal/*/, since that might be quite large, and should be correct anyway.
2014-06-11 12:23:16 +04:00
Z /run/log/journal/%m ~2750 root systemd-journal - -
build-sys: allow references to wheel group to be omitted https://github.com/systemd/systemd/issues/2492
2016-02-15 19:08:26 +03:00
m4_ifdef(`HAVE_ACL',
m4_ifdef(`ENABLE_WHEEL_GROUP',``
tmpfiles: use ACL magic on journal directories
2015-01-18 23:05:40 +03:00
a+ /run/log/journal/%m - - - - d:group:adm:r-x,d:group:wheel:r-x
A+ /run/log/journal/%m - - - - group:adm:r-x,group:wheel:r-x
build-sys: allow references to wheel group to be omitted https://github.com/systemd/systemd/issues/2492
2016-02-15 19:08:26 +03:00
'',``
a+ /run/log/journal/%m - - - - d:group:adm:r-x
A+ /run/log/journal/%m - - - - group:adm:r-x
''))m4_dnl
tmpfiles: don't allow read access to journal files to users not in systemd-journal Also, don't apply access mode recursively to /var/log/journal/*/, since that might be quite large, and should be correct anyway.
2014-06-11 12:23:16 +04:00
z /var/log/journal 2755 root systemd-journal - -
z /var/log/journal/%m 2755 root systemd-journal - -
tmpfiles: set acls on system.journal explicitly https://github.com/systemd/systemd/issues/1397
2015-11-30 02:48:40 +03:00
z /var/log/journal/%m/system.journal 0640 root systemd-journal - -
build-sys: allow references to wheel group to be omitted https://github.com/systemd/systemd/issues/2492
2016-02-15 19:08:26 +03:00
m4_ifdef(`HAVE_ACL',
m4_ifdef(`ENABLE_WHEEL_GROUP',``
tmpfiles: also set acls on /var/log/journal This way, directories created later for containers or for journald-remote, will be readable by adm & wheel groups by default, similarly to /var/log/journal/%m itself. https://github.com/systemd/systemd/issues/1971
2015-11-30 02:37:01 +03:00
a+ /var/log/journal - - - - d:group:adm:r-x,d:group:wheel:r-x
a+ /var/log/journal - - - - group:adm:r-x,group:wheel:r-x
tmpfiles: use ACL magic on journal directories
2015-01-18 23:05:40 +03:00
a+ /var/log/journal/%m - - - - d:group:adm:r-x,d:group:wheel:r-x
tmpfiles: don't recursively descend into journal directories in /var Do so only in /run. We shouldn't alter ACLs for existing files in /var, but only for new files. If the admin made changes to the ACLs they shouls stay in place. We should still do recursive ACL changes for files in /run, since those are not persistent, and will hence lack ACLs on every boot. Also, /var/log/journal might be quit large, /run/log/journal is usually not, hence we should avoid the recursive descending on /var, but not on /run. Fixes #534
2015-07-10 00:43:55 +03:00
a+ /var/log/journal/%m - - - - group:adm:r-x,group:wheel:r-x
tmpfiles: set acls on system.journal explicitly https://github.com/systemd/systemd/issues/1397
2015-11-30 02:48:40 +03:00
a+ /var/log/journal/%m/system.journal - - - - group:adm:r--,group:wheel:r--
build-sys: allow references to wheel group to be omitted https://github.com/systemd/systemd/issues/2492
2016-02-15 19:08:26 +03:00
'',``
a+ /var/log/journal - - - - d:group:adm:r-x
a+ /var/log/journal - - - - group:adm:r-x
a+ /var/log/journal/%m - - - - d:group:adm:r-x
a+ /var/log/journal/%m - - - - group:adm:r-x
a+ /var/log/journal/%m/system.journal - - - - group:adm:r--
''))m4_dnl
tmpfiles: automatically clean up /var/lib/systemd/coredump after 3d
2014-06-19 00:06:25 +04:00
d /var/lib/systemd 0755 root root -
d /var/lib/systemd/coredump 0755 root root 3d
Copy Permalink