shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2025-03-15 06:50:17 +03:00
Code
systemd/tmpfiles.d/systemd.conf

32 lines
1.0 KiB
Plaintext
Raw Permalink Normal View History

tmpfiles: install default tmpfiles configuration
2010-09-28 22:32:53 +02: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 00:20:58 +02: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-28 22:32:53 +02:00
# (at your option) any later version.
tmpfiles: include reference to man page in tmpfiles files
2010-11-10 23:58:01 +01:00
# See tmpfiles.d(5) for details
tmpfiles: exclude the first level directories in /run/user from automatic clean up It's logind's job to maintain those user dirs, so avoid automatic clean up for them. However, we do cover everything within them.
2012-06-20 09:05:50 +02:00
d /run/user 0755 root root ~10d
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-20 20:25:39 -05: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 00:43:28 +02:00
tmpfiles: Make wtmp match utmp perms, and add btmp.
2010-10-21 22:37:17 -04:00
f /var/log/wtmp 0664 root utmp -
f /var/log/btmp 0600 root utmp -
tmpfiles: integrate kay's directory cleanup code and otherwise beef up tmpfiles quite a bit
2010-10-18 22:38:41 +02:00
d /var/cache/man - - - 30d
tmpfiles: remove forcefsck/fastboot flag files after boot
2010-10-19 19:35:04 +02:00
path: optionally, create watched directories in .path units
2011-04-10 01:30:14 +02:00
d /run/systemd/ask-password 0755 root root -
sd-login: beef up login api, to add monitoring and enumerating
2011-07-22 21:01:15 +02: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 03:47:23 +02: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 02:04:46 +02:00
d /run/systemd/shutdown 0755 root root -
network: always create /run/systemd/network/links This ways the networkd client library should work even if networkd is not running. http://lists.freedesktop.org/archives/systemd-devel/2014-May/019242.html
2014-05-16 15:56:44 +02:00
d /run/systemd/network 0755 root root -
d /run/systemd/network/links 0755 root root -
timesyncd: order after tmpfiles to get a working network monitor
2014-05-22 07:55:38 +09:00
d /run/systemd/network/leases 0755 root root -
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 17:35:13 +02:00
journald: avoid NSS in journald In order to avoid a deadlock between journald looking up the "systemd-journal" group name, and nscd (or anyother NSS backing daemon) logging something back to the journal avoid all NSS in journald the same way as we avoid it from PID 1. With this change we rely on the kernel file system logic to adjust the group of created journal files via the SETGID bit on the journal directory. To ensure that it is always set, even after the user created it with a simply "mkdir" on the shell we fix it up via tmpfiles on boot.
2013-09-17 16:42:36 -05:00
m /var/log/journal 2755 root systemd-journal - -
tmpfiles: fix permissions on new journal files When starting up journald on a new system, set the proper permissions on the system.journal files, not only on the journal directory.
2014-04-15 14:12:01 -07:00
Z /var/log/journal/%m 2755 root systemd-journal - -
tmpfiles.d: include setgid perms for /run/log/journal 4608af4333d0f7f5 set permissions for journal storage on persistent disk but not the volatile storage. ref: https://bugs.archlinux.org/task/37170
2013-10-02 15:35:16 -04:00
m /run/log/journal 2755 root systemd-journal - -
tmpfiles: fix permissions on new journal files When starting up journald on a new system, set the proper permissions on the system.journal files, not only on the journal directory.
2014-04-15 14:12:01 -07:00
Z /run/log/journal/%m 2755 root systemd-journal - -
Copy Permalink