| /systemd-251/docs/ |
| D | TEMPORARY_DIRECTORIES.md | 10 `/tmp/` and `/var/tmp/` are two world-writable directories Linux systems
26 for details about these two (and most other) directories of a Linux system.
41 directories are pre-created during early boot, and thus problematic if package
62 `/var/tmp/` are replaced by private sub-directories, implemented through Linux
65 reality they are private sub-directories of the host's real `/tmp/` and
74 directories are removed whenever the service shuts down, hence the lifecycle of
77 `/var/tmp/` for sharing files and directories. If this option is turned on this
79 both directories.
84 and directories stored in `/tmp/` and `/var/tmp/`. This means that files that
92 directories doesn't grow without bounds, even when programs abort unexpectedly
[all …]
|
| D | HOME_DIRECTORY.md | 11 manages home directories of regular ("human") users. Each directory it manages
15 the format used by these home directories, in the context of the storage
41 It is recommended to name home directories managed this way by
46 active. `systemd-homed` will automatically discover home directories named this
76 for all other storage mechanisms it is entirely sufficient if the directories
140 the contained file system: this way special directories such as `lost+found/`
152 active and inactive home directories, so that the directories become
|
| D | ENVIRONMENT.md | 290 `/opt/` are managed, and directories may be added or removed to that list by
292 paths. Only "real" file systems and directories that only contain "real" file
303 lines will always create directories.
336 prefer creating btrfs subvolumes over plain directories for machine
343 directories, because btrfs subvolumes are not supported or disabled. If
376 directories in `/usr/lib/`, `/run`, …) or passed to the kernel for validation
409 directories/images. When unspecified defaults to `/home/`. This is useful for
411 operates on a different directory where home directories/images are placed.
440 use for LUKS home directories, overriding the built-in default mount
|
| D | BUILDING_IMAGES.md | 72 entries and the directories in the ESP to place kernel images in. This is done
106 will create a couple of directories strictly necessary to boot up
125 component ensures that various files and directories below `/etc/`, `/var/`
127 directories/symlinks created by the `switch-root` logic above this logic is
141 configuration data in `/etc/` or their state directories in `/var/` are
143 ensure the missing files and directories are created if missing. In particular,
|
| D | UIDS-GIDS.md | 100 1. 60001…60513 → UIDs for home directories managed by
236 5. `systemd-homed` by default mounts the home directories it manages with UID
240 files/directories in home directories managed by `systemd-homed` cannot be
248 files/directories not owned by the home directory's user) in home directories
253 restricts compatibility with networked home directories. Typically, it's a much
|
| D | USERDB_AND_DESKTOPS.md | 12 for managing regular ("human") users and their home directories. Along with it
31 One key feature of `systemd-homed` managed encrypted home directories is the
36 for the home directories remained in memory during system suspend, so that
68 to set this parameter to on. `systemd-homed` will not suspend home directories
|
| D | PORTABLE_SERVICES.md | 40 doesn't define any new metadata as unit files and OS tree directories or disk
186 6. The image must contain directories `/proc/`, `/sys/`, `/dev/`, `/run/`,
190 7. The OS might require other files or directories to be in place. For example,
224 If the image is writable, and some of the files or directories that are
226 On read-only, immutable images (e.g. squashfs images) all files and directories
|
| D | BOOT_LOADER_SPECIFICATION.md | 54 * Drop-in directories are otherwise now pretty ubiquitous on Linux as an easy
165 files and directories in the same file system. For example, boot loaders that
169 if files or directories other than `/loader/` are found in the top level
170 directory. Implementations that add their own files or directories to the file
171 systems should use well-named directories, to make name collisions between
176 We define two directories below `$BOOT`:
|
| D | USER_GROUP_API.md | 23 records may be dropped in number of drop-in directories as files where they are
126 directories it manages.
135 enforced by systemd and defined directly in LDAP directories.
|
| D | USER_RECORD.md | 16 manages `human` user home directories and embeds these JSON records
80 also be dropped in number of drop-in directories as files. See
197 purposes. Inside the home directories (and if the LUKS2 backend is used, also
360 `systemd-homed` when managing home directories, but may be used if other
404 directories. Note that these booleans are only honored if the home directory
406 mounts home directories on login.
756 is generally persisted on the system but not in the home directories themselves
876 `stopDelayUSec` if the field is not explicitly specified: for home directories
922 disk images. User records and home directories in many context are expected to
|
| D | CONTAINER_INTERFACE.md | 70 root-level cgroup directories tend to be quite different from inner
71 directories, and that distinction matters. It is OK however, to mount the
90 Do not add new cgroup directories to the top of the tree. This will not only
335 sub-directories of `/sys/` writable, but make sure to leave the root of
|
| D | index.md | 12 … and running containers and virtual machines, system accounts, runtime directories and settings, a…
|
| /systemd-251/src/core/ |
| D | execute.c | 1956 if (c->directories[t].n_items == 0) in build_environment()
1963 for (size_t i = 0; i < c->directories[t].n_items; i++) { in build_environment()
1966 prefixed = path_join(p->prefix[t], c->directories[t].items[i].path); in build_environment()
2090 if (context->directories[t].n_items > 0) in exec_needs_mount_namespace()
2096 (context->directories[EXEC_DIRECTORY_STATE].n_items > 0 || in exec_needs_mount_namespace()
2097 context->directories[EXEC_DIRECTORY_CACHE].n_items > 0 || in exec_needs_mount_namespace()
2098 context->directories[EXEC_DIRECTORY_LOGS].n_items > 0)) in exec_needs_mount_namespace()
2341 for (size_t i = 0; i < context->directories[type].n_items; i++) { in setup_exec_directory()
2344 p = path_join(params->prefix[type], context->directories[type].items[i].path); in setup_exec_directory()
2391 if (!path_extend(&pp, context->directories[type].items[i].path)) { in setup_exec_directory()
[all …]
|
| D | dbus-execute.c | 1277 …k", "a(sst)", bus_property_get_exec_dir_symlink, offsetof(ExecContext, directories[EXEC_DIRECTORY_…
1279 …ntimeDirectoryMode", "u", bus_property_get_mode, offsetof(ExecContext, directories[EXEC_DIRECTORY_…
1280 …timeDirectory", "as", bus_property_get_exec_dir, offsetof(ExecContext, directories[EXEC_DIRECTORY_…
1281 …k", "a(sst)", bus_property_get_exec_dir_symlink, offsetof(ExecContext, directories[EXEC_DIRECTORY_…
1282 …StateDirectoryMode", "u", bus_property_get_mode, offsetof(ExecContext, directories[EXEC_DIRECTORY_…
1283 …tateDirectory", "as", bus_property_get_exec_dir, offsetof(ExecContext, directories[EXEC_DIRECTORY_…
1284 …k", "a(sst)", bus_property_get_exec_dir_symlink, offsetof(ExecContext, directories[EXEC_DIRECTORY_…
1285 …CacheDirectoryMode", "u", bus_property_get_mode, offsetof(ExecContext, directories[EXEC_DIRECTORY_…
1286 …acheDirectory", "as", bus_property_get_exec_dir, offsetof(ExecContext, directories[EXEC_DIRECTORY_…
1287 …k", "a(sst)", bus_property_get_exec_dir_symlink, offsetof(ExecContext, directories[EXEC_DIRECTORY_…
[all …]
|
| D | load-fragment-gperf.gperf.in | 136 … 0, offsetof({{type}}, exec_context.directories[EXEC_DIRECTORY_…
137 … 0, offsetof({{type}}, exec_context.directories[EXEC_DIRECTORY_…
138 … 0, offsetof({{type}}, exec_context.directories[EXEC_DIRECTORY_…
139 … 0, offsetof({{type}}, exec_context.directories[EXEC_DIRECTORY_…
140 … 0, offsetof({{type}}, exec_context.directories[EXEC_DIRECTORY_…
141 … 0, offsetof({{type}}, exec_context.directories[EXEC_DIRECTORY_…
142 … 0, offsetof({{type}}, exec_context.directories[EXEC_DIRECTORY_…
143 … 0, offsetof({{type}}, exec_context.directories[EXEC_DIRECTORY_…
144 … 0, offsetof({{type}}, exec_context.directories[EXEC_DIRECTORY_…
145 … 0, offsetof({{type}}, exec_context.directories[EXEC_DIRECTORY_…
|
| D | execute.h | 344 ExecDirectory directories[_EXEC_DIRECTORY_TYPE_MAX]; member
|
| /systemd-251/shell-completion/zsh/ |
| D | _systemd-tmpfiles | 8 '--clean[Clean up all files and directories with an age parameter configured.]' \
9 '--remove[All files and directories marked with r, R in the configuration files are removed.]' \
|
| D | _journalctl | 124 …e --root --file)'{-D+,--directory=}'[Show journal files from directory]:directories:_directories' \
125 … --file)--root=[Operate on catalog hierarchy under specified directory]:directories:_directories' \
|
| D | _systemd-nspawn | 19 …he namespace container. If omitted the current directory will be used.]:directories:_directories' \
|
| /systemd-251/src/shared/ |
| D | exec-util.c | 83 char **directories, in do_execute() argument
105 …NF_FILES_EXECUTABLE|CONF_FILES_REGULAR|CONF_FILES_FILTER_MASKED, (const char* const*) directories); in do_execute()
194 const char* const* directories, in execute_directories() argument
202 char **dirs = (char**) directories; in execute_directories()
|
| D | exec-util.h | 34 const char* const* directories,
|
| /systemd-251/tmpfiles.d/ |
| D | README | 2 to create, delete, and clean up volatile and temporary files and directories.
|
| /systemd-251/test/test-execute/ |
| D | exec-temporaryfilesystem-rw.service | 8 # Check directories exist
|
| D | exec-temporaryfilesystem-ro.service | 8 # Check directories exist
|
| /systemd-251/ |
| D | NEWS | 167 of activated home directories it manages (if the kernel and selected
197 handling, and improving compatibility with home directories intended
245 ExtensionImages=, but takes paths to directories, instead of
343 /etc/credstore/, /run/credstore/, /usr/lib/credstore/ directories if
345 LoadCredentialEncrypted= will check the same directories plus
347 /usr/lib/credstore.encrypted/. The idea is to use those directories
755 and the specified directories are also added the $PATH environment
766 specified directory. This allows creating these service directories
1051 files/directories bound into containers will no longer show up as
1109 specific to a single boot entry), or in one of the shared directories
[all …]
|