shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-12-22 17:35:35 +03:00
Code
main
systemd/presets/90-systemd.preset

55 lines
1.5 KiB
Plaintext
Raw Permalink Normal View History

license: LGPL-2.1+ -> LGPL-2.1-or-later
2020-11-09 07:23:58 +03:00
# SPDX-License-Identifier: LGPL-2.1-or-later
Add SPDX license headers to various assorted files
2017-11-18 20:18:16 +03:00
#
preset: ship a minimal preset file upstream This is useful so that distros have something to base their own policy of. It also useful to make sure that minimal installs always get useful configuration in place.
2014-06-17 03:14:44 +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.
presets: "disable" all passive targets by default Officially we default to a "enable *", even though pretty much everybody overrides this with "disable *". We have a bunch of targets and services which should not be enabled by default. In case the default policy is not overriden, our passive units would be enabled by presets, which is generally not useful at all. So let's explicitly mark them as disabled. Note that this effectively changes very little. E.g. on Fedora, all the units listed in this patch were "disabled" already. Fixes #14648.
2020-02-03 17:45:07 +03:00
# Settings for systemd units distributed with systemd itself. Most of these
# should be enabled by default, even if the distribution follows a general
# default-off policy.
preset: ship a minimal preset file upstream This is useful so that distros have something to base their own policy of. It also useful to make sure that minimal installs always get useful configuration in place.
2014-06-17 03:14:44 +04:00
enable remote-fs.target
units: add [Install] section to remote-cryptsetup.target This makes this target the same as remote-fs.target in this regard. In practice it probably doesn't make that much difference, because all encrypted devices that are part of remote-fs.target (marked with _netdev) will be used for mount points, so they will be pulled in anyway individually, but with this change any such device will be configured, even if it is not pulled by any other unit.
2017-10-12 23:13:03 +03:00
enable remote-cryptsetup.target
preset: enable machines.target by default
2014-12-29 19:36:57 +03:00
enable machines.target
preset: ship a minimal preset file upstream This is useful so that distros have something to base their own policy of. It also useful to make sure that minimal installs always get useful configuration in place.
2014-06-17 03:14:44 +04:00
enable getty@.service
preset: add some alphabetical sorting I think the existing sections in the preset file make sense, but alphabetical ordering is kinda cool too. try to find a middle ground, and at least sort within each section. No actual change of behaviour, just some reordering of lines.
2024-01-23 18:52:56 +03:00
enable systemd-boot-update.service
preset: enable confext and sysext by default (#31211)
2024-02-06 23:19:59 +03:00
enable systemd-confext.service
preset: add some alphabetical sorting I think the existing sections in the preset file make sense, but alphabetical ordering is kinda cool too. try to find a middle ground, and at least sort within each section. No actual change of behaviour, just some reordering of lines.
2024-01-23 18:52:56 +03:00
enable systemd-homed.service
preset: enable homed sidecar services As described in https://github.com/systemd/systemd/issues/31235, the preset state for systemd-homed-activate.service was unclear. On the one hand, we have a preset with 'enable systemd-homed.service', and systemd-homed.service has 'Also=systemd-homed-activate.service systemd-homed-firstboot.service', so 'preset systemd-homed.service' would also enable those two services, but 'preset systemd-homed-activate.service' would disable it, because the presets don't say it is enabled. It seems that this configuration is internally inconsistent. As described in the issue, maybe systemctl should be smarter here, or warn about such configs. Either way, let's make our config consistent. Follow-up for d1f6e01e4743ae94740314eeb46a162112ef4599 and 3ccadbce3358ba1db7ce5fa3f8dd17c627ffd93b.
2024-02-07 14:43:53 +03:00
enable systemd-homed-activate.service
preset: add some alphabetical sorting I think the existing sections in the preset file make sense, but alphabetical ordering is kinda cool too. try to find a middle ground, and at least sort within each section. No actual change of behaviour, just some reordering of lines.
2024-01-23 18:52:56 +03:00
enable systemd-journald-audit.socket
mountfsd: add new systemd-mountfsd component
2023-03-09 14:27:29 +03:00
enable systemd-mountfsd.socket
preset: add some alphabetical sorting I think the existing sections in the preset file make sense, but alphabetical ordering is kinda cool too. try to find a middle ground, and at least sort within each section. No actual change of behaviour, just some reordering of lines.
2024-01-23 18:52:56 +03:00
enable systemd-network-generator.service
nsresourced: add new daemon for granting clients user namespaces and assigning resources to them This adds a small, socket-activated Varlink daemon that can delegate UID ranges for user namespaces to clients asking for it. The primary call is AllocateUserRange() where the user passes in an uninitialized userns fd, which is then set up. There are other calls that allow assigning a mount fd to a userns allocated that way, to set up permissions for a cgroup subtree, and to allocate a veth for such a user namespace. Since the UID assignments are supposed to be transitive, i.e. not permanent, care is taken to ensure that users cannot create inodes owned by these UIDs, so that persistancy cannot be acquired. This is implemented via a BPF-LSM module that ensures that any member of a userns allocated that way cannot create files unless the mount it operates on is owned by the userns itself, or is explicitly allowelisted. BPF LSM program with contributions from Alexei Starovoitov.
2023-04-20 20:07:33 +03:00
enable systemd-networkd.service
mountfsd: add new systemd-mountfsd component
2023-03-09 14:27:29 +03:00
enable systemd-networkd-wait-online.service
nsresourced: add new daemon for granting clients user namespaces and assigning resources to them This adds a small, socket-activated Varlink daemon that can delegate UID ranges for user namespaces to clients asking for it. The primary call is AllocateUserRange() where the user passes in an uninitialized userns fd, which is then set up. There are other calls that allow assigning a mount fd to a userns allocated that way, to set up permissions for a cgroup subtree, and to allocate a veth for such a user namespace. Since the UID assignments are supposed to be transitive, i.e. not permanent, care is taken to ensure that users cannot create inodes owned by these UIDs, so that persistancy cannot be acquired. This is implemented via a BPF-LSM module that ensures that any member of a userns allocated that way cannot create files unless the mount it operates on is owned by the userns itself, or is explicitly allowelisted. BPF LSM program with contributions from Alexei Starovoitov.
2023-04-20 20:07:33 +03:00
enable systemd-nsresourced.socket
preset: add some alphabetical sorting I think the existing sections in the preset file make sense, but alphabetical ordering is kinda cool too. try to find a middle ground, and at least sort within each section. No actual change of behaviour, just some reordering of lines.
2024-01-23 18:52:56 +03:00
enable systemd-pstore.service
preset: ship a minimal preset file upstream This is useful so that distros have something to base their own policy of. It also useful to make sure that minimal installs always get useful configuration in place.
2014-06-17 03:14:44 +04:00
enable systemd-resolved.service
preset: enable confext and sysext by default (#31211)
2024-02-06 23:19:59 +03:00
enable systemd-sysext.service
preset: add some alphabetical sorting I think the existing sections in the preset file make sense, but alphabetical ordering is kinda cool too. try to find a middle ground, and at least sort within each section. No actual change of behaviour, just some reordering of lines.
2024-01-23 18:52:56 +03:00
enable systemd-timesyncd.service
units: make systemd-userdbd.{socket,service} installable It's lightweight and generally useful, so it should be enabled by default. But users might want to disable it for whatever reason, and things should be fine without it, so let's make it installable so it can be disabled if wanted. Fixes #15175.
2020-03-13 20:40:54 +03:00
enable systemd-userdbd.socket
preset: ship a minimal preset file upstream This is useful so that distros have something to base their own policy of. It also useful to make sure that minimal installs always get useful configuration in place.
2014-06-17 03:14:44 +04:00
disable console-getty.service
disable debug-shell.service
preset: add some alphabetical sorting I think the existing sections in the preset file make sense, but alphabetical ordering is kinda cool too. try to find a middle ground, and at least sort within each section. No actual change of behaviour, just some reordering of lines.
2024-01-23 18:52:56 +03:00
disable exit.target
preset: ship a minimal preset file upstream This is useful so that distros have something to base their own policy of. It also useful to make sure that minimal installs always get useful configuration in place.
2014-06-17 03:14:44 +04:00
disable halt.target
disable kexec.target
disable poweroff.target
units: synchronize Makefile and presets settings Enable reboot.target and disable exit.target: the first is used on normal machines, the second only in containers, and the more general one should be enabled by default. Also fix the Makefile to match what preset-all does. With this and the previous commits, doing "make instal DESTDIR=…" followed by "systemctl preset-all --root=…" doesn't result in any changes.
2016-08-13 08:55:16 +03:00
enable reboot.target
preset: ship a minimal preset file upstream This is useful so that distros have something to base their own policy of. It also useful to make sure that minimal installs always get useful configuration in place.
2014-06-17 03:14:44 +04:00
disable rescue.target
preset: don't enable proc-sys-fs-binfmt_misc.mount The proc-sys-fs-binfmt_misc.mount unit should not be enabled by preset-all because it should only be used as fallback in case proc-sys-fs-binfmt_misc.automount cannot be used on a system. In these cases it should be enabled manually by an administrator.
2020-09-06 22:23:36 +03:00
disable proc-sys-fs-binfmt_misc.mount
preset: let's clean up preset list a bit let's make sure we list all singleton units we define in the preset list, either as disable or as enable. Only four were missing, let's add them in. Also, let's group the pstore one with the other ones that are enabled, right at the top.
2020-04-07 20:01:00 +03:00
preset: ship a minimal preset file upstream This is useful so that distros have something to base their own policy of. It also useful to make sure that minimal installs always get useful configuration in place.
2014-06-17 03:14:44 +04:00
disable syslog.socket
preset: add some alphabetical sorting I think the existing sections in the preset file make sense, but alphabetical ordering is kinda cool too. try to find a middle ground, and at least sort within each section. No actual change of behaviour, just some reordering of lines.
2024-01-23 18:52:56 +03:00
disable systemd-boot-check-no-failures.service
preset: ship a minimal preset file upstream This is useful so that distros have something to base their own policy of. It also useful to make sure that minimal installs always get useful configuration in place.
2014-06-17 03:14:44 +04:00
disable systemd-journal-gatewayd.*
units: enable systemd-networkd-wait-online.service, disable all journal-remote stuff The preset for systemd-networkd-wait-online.service should match whatever we do for systemd-networkd.service. s-n-wait-online.service is only pulled in when some other unit pulls in network-online.target, otherwise it's not used. But if something pulls in network-online.target, they should expect s-n-wait-online.service to be active iff systemd-networkd.service is active. OTOH, the journal-remote and journal-upload services should be disabled by default, since they don't do anything without additional configuration.
2016-08-13 08:52:12 +03:00
disable systemd-journal-remote.*
disable systemd-journal-upload.*
preset: add some alphabetical sorting I think the existing sections in the preset file make sense, but alphabetical ordering is kinda cool too. try to find a middle ground, and at least sort within each section. No actual change of behaviour, just some reordering of lines.
2024-01-23 18:52:56 +03:00
disable systemd-time-wait-sync.service
Copy Permalink