shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-11-05 15:21:37 +03:00
Code
0f7c9a3d81
systemd/tmpfiles.d/etc.conf.m4

23 lines
700 B
Plaintext
Raw Normal View History

tmpfiles: add minimal tmpfiles snippet to rebuild the most essential stuff from /etc
2014-06-13 15:29:25 +04:00
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# 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
# (at your option) any later version.
# See tmpfiles.d(5) for details
L /etc/os-release - - - - ../usr/lib/os-release
tmpfiles: add new "L+" command as stronger version of "L", that removes the destination before creating a symlink Also, make use of this for mtab as long as mount insists on creating it even if we invoke it with "-n".
2014-06-16 15:21:07 +04:00
L+ /etc/mtab - - - - ../proc/self/mounts
smack: label /etc/mtab as "_" when '--with-smack-run-label' is enabled. /etc/mtab should be labeled as "_", even though systemd has its own smack label using '--with-smack-run-label' configuration. This is mainly because all processes could read that file and the origin of this file (i.e. /proc/mounts) is labeled as "_". This labels /etc/mtab as "_" when '--with-smack-run-label' is enabled.
2015-09-10 15:52:39 +03:00
m4_ifdef(`HAVE_SMACK_RUN_LABEL',
t /etc/mtab - - - - security.SMACK64=_
)m4_dnl
build-sys: s/ENABLE_RESOLVED/ENABLE_RESOLVE/ The configuration option was called -Dresolve, but the internal define was …RESOLVED. This options governs more than just resolved itself, so let's settle on the version without "d".
2017-10-03 14:12:29 +03:00
m4_ifdef(`ENABLE_RESOLVE',
resolved: create private stub resolve file for /etc/resolv.conf integration (#7014) This creates a second private resolve.conf file which lists the stub resolver and the resolved acquired search domains. This runtime file should be used as a symlink target for /etc/resolv.conf such that non-nss based applications can resolve search domains. Fixes: #7009
2017-10-24 16:28:41 +03:00
L! /etc/resolv.conf - - - - ../run/systemd/resolve/stub-resolv.conf
tmpfiles: Remove unnecessary blank line when configured with "--disable-resolved" This patch removes unnecessary blank line in /usr/lib/tmpfiles.d/etc.conf when configured with "--disable-resolved". (i.e. ENABLE_RESOLVED is not defined)
2015-02-02 14:25:02 +03:00
)m4_dnl
tmpfiles: copy files to /etc only on boot We'd copy /etc/nsswitch.conf, /etc/pam.d/, and /etc/issue (*) on every tmpfiles --create run. I think we should only do this at boot, so if people install systemd.rpm in a larger transaction and want to create those files at a later step, we don't interfere with that. (Stuff like /etc/os-release and /etc/mtab is not really configurable, we might as was create it uncondtionally.) (Seemingly, the alternative approach might be to not call systemd-tmpfiles --create in systemd.rpm %post. But this wouldn't have much effect, because various packages call it anyway, and our %tmpfiles_create_package macro does too. So we need to change the configuration instead.) (*) We don't provide /usr/share/factory/issue, so normally this fails, but somebody else might provide that file, so it seems useful to keep the C line.
2019-07-25 20:13:41 +03:00
C! /etc/nsswitch.conf - - - -
tmpfiles.d: only copy /etc/pam.d if PAM is present If HAVE_PAM isn't set then don't attempt to copy /etc/pam.d from the factory, as it doesn't get installed.
2015-03-03 14:37:52 +03:00
m4_ifdef(`HAVE_PAM',
tmpfiles: copy files to /etc only on boot We'd copy /etc/nsswitch.conf, /etc/pam.d/, and /etc/issue (*) on every tmpfiles --create run. I think we should only do this at boot, so if people install systemd.rpm in a larger transaction and want to create those files at a later step, we don't interfere with that. (Stuff like /etc/os-release and /etc/mtab is not really configurable, we might as was create it uncondtionally.) (Seemingly, the alternative approach might be to not call systemd-tmpfiles --create in systemd.rpm %post. But this wouldn't have much effect, because various packages call it anyway, and our %tmpfiles_create_package macro does too. So we need to change the configuration instead.) (*) We don't provide /usr/share/factory/issue, so normally this fails, but somebody else might provide that file, so it seems useful to keep the C line.
2019-07-25 20:13:41 +03:00
C! /etc/pam.d - - - -
tmpfiles.d: only copy /etc/pam.d if PAM is present If HAVE_PAM isn't set then don't attempt to copy /etc/pam.d from the factory, as it doesn't get installed.
2015-03-03 14:37:52 +03:00
)m4_dnl
tmpfiles: copy files to /etc only on boot We'd copy /etc/nsswitch.conf, /etc/pam.d/, and /etc/issue (*) on every tmpfiles --create run. I think we should only do this at boot, so if people install systemd.rpm in a larger transaction and want to create those files at a later step, we don't interfere with that. (Stuff like /etc/os-release and /etc/mtab is not really configurable, we might as was create it uncondtionally.) (Seemingly, the alternative approach might be to not call systemd-tmpfiles --create in systemd.rpm %post. But this wouldn't have much effect, because various packages call it anyway, and our %tmpfiles_create_package macro does too. So we need to change the configuration instead.) (*) We don't provide /usr/share/factory/issue, so normally this fails, but somebody else might provide that file, so it seems useful to keep the C line.
2019-07-25 20:13:41 +03:00
C! /etc/issue - - - -
Copy Permalink