Searched refs:drop (Results 1 – 25 of 37) sorted by relevance
12
| /systemd-251/src/basic/ |
| D | capability-util.c | 401 uint64_t combined, drop = 0; in capability_quintet_mangle() local
420 drop |= bit; in capability_quintet_mangle()
425 q->effective &= ~drop; in capability_quintet_mangle()
426 q->bounding &= ~drop; in capability_quintet_mangle()
427 q->inheritable &= ~drop; in capability_quintet_mangle()
428 q->permitted &= ~drop; in capability_quintet_mangle()
431 q->ambient &= ~drop; in capability_quintet_mangle()
433 return drop != 0; /* Let the caller know we changed something */ in capability_quintet_mangle()
|
| /systemd-251/src/basic/linux/ |
| D | README | 5 - btrfs.h: drop '__user' attributes
6 - if.h: drop '#include <linux/compiler.h>' and '__user' attributes
|
| /systemd-251/src/timesync/ |
| D | timesyncd.conf.in | 9 # should be created by either modifying this file, or by creating "drop-ins" in
11 # Defaults can be restored by simply deleting this file and all drop-ins.
|
| /systemd-251/src/journal-remote/ |
| D | journal-remote.conf.in | 9 # should be created by either modifying this file, or by creating "drop-ins" in
11 # Defaults can be restored by simply deleting this file and all drop-ins.
|
| D | journal-upload.conf.in | 9 # should be created by either modifying this file, or by creating "drop-ins" in
11 # Defaults can be restored by simply deleting this file and all drop-ins.
|
| /systemd-251/src/core/ |
| D | user.conf.in | 9 # should be created by either modifying this file, or by creating "drop-ins" in
11 # Defaults can be restored by simply deleting this file and all drop-ins.
|
| D | system.conf.in | 9 # should be created by either modifying this file, or by creating "drop-ins" in
11 # Defaults can be restored by simply deleting this file and all drop-ins.
|
| /systemd-251/src/login/ |
| D | logind.conf.in | 9 # should be created by either modifying this file, or by creating "drop-ins" in
11 # Defaults can be restored by simply deleting this file and all drop-ins.
|
| /systemd-251/src/resolve/ |
| D | resolved.conf.in | 9 # should be created by either modifying this file, or by creating "drop-ins" in
11 # Defaults can be restored by simply deleting this file and all drop-ins.
|
| /systemd-251/src/delta/ |
| D | delta.c | 193 const char *toppath, const char *drop) { in enumerate_dir_d() argument
201 assert(!endswith(drop, "/")); in enumerate_dir_d()
203 path = path_join(toppath, drop); in enumerate_dir_d()
209 unit = strdup(drop); in enumerate_dir_d()
|
| /systemd-251/docs/ |
| D | DESKTOP_ENVIRONMENTS.md | 76 adjusted using desktop environment specific drop-in files.
84 currently using a drop-in to configure `BindTo=graphical-session.target`,
91 * Could we maybe add a default `app-.service.d` drop-in configuration?
|
| D | BOOT_LOADER_SPECIFICATION.md | 14 single boot configuration format that is based on drop-in files, and thus is
20 drop-in files for boot menu items that are defined in a format that is shared
26 configuration at runtime from these drop-in snippets
34 up the initial drop-in directory
70 drop-in files exclusively.
134 was traditionally handled), all installed OS share the same place to drop in
181 * `$BOOT/loader/entries/` is the directory containing the drop-in
189 Inside the `$BOOT/loader/entries/` directory each OS vendor may drop one or
277 Each configuration drop-in snippet must include at least a `linux` or an `efi`
278 key and is otherwise not valid. Here's an example for a complete drop-in file:
|
| D | PORTABLE_SERVICES.md | 113 3. For each such unit file a drop-in file is created. Let's say
115 `/etc/systemd/system.attached/`, then a drop-in file
126 4. For each such unit a "profile" drop-in is linked in. This "profile" drop-in
139 written to the unit drop-in would point to an non-existent path, and break
143 the drop-ins and the unit files associated with the image, and removes them.
|
| D | BOOT_LOADER_INTERFACE.md | 119 [Boot Loader Specification](BOOT_LOADER_SPECIFICATION.md) drop-in files
120 the identifier should be derived directly from the drop-in snippet name, but
|
| /systemd-251/network/ |
| D | 80-wifi-adhoc.network | 7 # 1. add a drop-in file that extends this file by creating the
|
| D | 99-default.link | 7 # 1. add a drop-in file that extends this file by creating the
|
| D | 80-6rd-tunnel.network | 7 # 1. add a drop-in file that extends this file by creating the
|
| D | 80-container-host0.network | 7 # 1. add a drop-in file that extends this file by creating the
|
| D | 80-container-vb.network | 7 # 1. add a drop-in file that extends this file by creating the
|
| D | 80-container-ve.network | 7 # 1. add a drop-in file that extends this file by creating the
|
| D | 80-container-vz.network | 7 # 1. add a drop-in file that extends this file by creating the
|
| D | 80-vm-vt.network | 7 # 1. add a drop-in file that extends this file by creating the
|
| /systemd-251/shell-completion/zsh/ |
| D | _systemd-nspawn | 38 …'--drop-capability=[Specify one or more additional capabilities to drop for the containerm]:capabi…
|
| /systemd-251/shell-completion/bash/ |
| D | systemd-nspawn | 67 …[ARG]='-D --directory -u --user --uuid --capability --drop-capability --link-journal --bind --bind…
95 --drop-capability)
|
| /systemd-251/ |
| D | TODO | 96 * given that /etc/ssh/ssh_config.d/ is a thing now, ship a drop-in for that
137 LoadCredential=root.ssh.authorized-keys via drop-in to
185 * drop support for kernels that lack ambient capabilities support (i.e. make
186 4.3 new baseline). Then drop support for "!!" modifier for ExecStart= which
212 type #2 drop-in dir in the ESP.
227 anything else but what we drop in via kernel-install, i.e. by earlier EFI
312 drop it into the unified kernel dir in the ESP. And bam you have something
329 authenticated, atomic, additive configuration management primitive: drop in a
466 similar to /run/host/userdb/. Usecase: drop a root user JSON record there,
471 * drop dependency on libcap, replace by direct syscalls based on
[all …]
|
12