| /systemd-251/tools/ |
| D | analyze-dump-sort.py | 26 same = []
42 if same and same[0].startswith(header):
43 same.append(line)
45 unit.extend(sorted(same, key=str.lower))
46 same = [line]
|
| /systemd-251/docs/ |
| D | GROUP_RECORD.md | 23 `realm` → The "realm" the group belongs to, conceptually identical to the same
28 they follow the same GECOS syntax requirements as `realName`.
31 same field of user records. A string.
59 same way as for the JSON user records, and have the same semantics.
76 equivalent to the fields of the same name in the `regular` section, and
84 to the fields of the same name in the `regular` and `perMachine` sections:
91 equivalent to the fields of the same name in the `regular` section, though with
92 slightly different conceptual semantics, see the same fields in the user record
128 The same logic and recommendations apply as for JSON user records.
|
| D | USER_GROUP_API.md | 62 enqueues the same query to each. The first positive reply is then returned to
84 multiple definitions for the same user or group, and will also not be able to
109 Both these services are implemented by the same daemon
151 forwarding. It is also possible to provide the same records via both APIs
214 being talked to (i.e. to the same name as the `AF_UNIX` socket path, with the
216 of multiple services on the same socket (which is used by
241 of daemons that provide multiple distinct user/group services over the same
259 allow implementation of multiple services within the same IPC socket. In case no
261 are also generated in the same cases as for `GetUserRecord` and
|
| D | JOURNAL_EXPORT_FORMATS.md | 16 …on-text data (though usually don't), and the same field might have multiple values assigned within…
129 …on-text data (though usually don't), and the same field might have multiple values assigned within…
135 * Within the same entry, Journal fields may have multiple values assigned. This is not allowed in J…
|
| D | CONVERTING_TO_HOMED.md | 49 related files. We want to use the same data for the new record, hence it's good
71 This will tell you the name of that group. If the name is the same as your
75 each user under the same name, hence if your distribution is one of the
90 account with `systemd-homed`, using the same username and UID as before:
|
| D | BOOT_LOADER_SPECIFICATION.md | 22 programs. The same scheme can be used to prepare OS media for cases where the
56 configuration files. For the sake of uniformity, we should do the same for
134 was traditionally handled), all installed OS share the same place to drop in
165 files and directories in the same file system. For example, boot loaders that
218 entries with the same title it is a good idea to show more than just the raw
223 install multiple kernel versions at the same time with the same `title`
267 applied in the same order as they are listed. This key is optional but
302 programs) that reside on the same file system as the configuration snippets,
303 i.e. everything referenced must be contained in the same file system. This is
335 Type #2 file names should be chosen from the same restricted character set as
[all …]
|
| D | PORTABLE_SERVICES.md | 60 services, can be controlled with the same tools, are exposed the same way in
64 would — but to run it in the same environment, but with stricter access
137 Note that the images need to stay around (and in the same location) as long as the
147 The same is true for the opposite `detach` operation.
269 portable services can share the same 'runtime' image (libraries, tools) without
313 Sometimes it makes sense to instantiate the same set of services multiple
326 The benefit of this approach is that templating works exactly the same for
|
| D | HOME_DIRECTORY.md | 95 record, in the same serialization as in `~/.identity`, though encrypted. The
98 encryption used is the same as the LUKS2 volume itself uses, unlocked by the
99 same volume key, but based on its own IV.
111 directory is mounted to the same path, though with the `.home` suffix dropped —
160 compared. Activation is only permitted if they match the same user and are
|
| D | CONTAINER_INTERFACE.md | 112 always pass the same UUID here. Keeping the externally used UUID for a
142 settings. The same protocol may be used to pass credentials from the
162 container into the same dir of the host. Administrators can then
182 hence the same as from the container manager to the container systemd. For
233 the same directory.
261 5. The `/run/host/container-manager` file may be used to pass the same
268 6. The `/run/host/container-uuid` file may be used to pass the same information
325 containers and the host would try to manage the same devices, fighting for
389 are unlikely to do the same.
392 out-of-the-box in containers. In fact we are interested to ensure that the same
|
| D | BUILDING_IMAGES.md | 23 Typically the same OS image shall be deployable in multiple instances, and each
33 up with the same ID and that will likely lead to problems sooner or later,
41 same random data that is included in the image, and thus possibly generate
42 random data that is more similar to other instances booted off the same
73 in order to allow multiple installations of the same OS on the same system
|
| D | PASSWORD_AGENTS.md | 10 …an `AF_UNIX`/`SOCK_DGRAM` socket. Multiple agents might be running at the same time in which case …
37 …same time. Your agent needs to be able to deal with that. Depending on your environment you may ei…
|
| D | JOURNAL_FILE_FORMAT.md | 59 usually don't), and the same field might have multiple values assigned within
60 the same entry.
308 entry (starting at 1) and are unique among all files which carry the same
310 creates its first file. All files generated by the same journal daemon instance
311 should hence carry the same seqnum_id. This should guarantee a monotonic stream
413 the same field name from the FIELD object of the field used.
491 between two entries that otherwise have the same sequence numbers and
495 plus their respective hashes (which are calculated the same way as in the DATA
499 number. For continuous parts of the file written during the same boot
500 (i.e. with the same boot_id) the monotonic timestamp is monotonic too. Modulo
[all …]
|
| D | GVARIANT-SERIALIZATION.md | 63 The first four bytes of the header are defined the same way for dbus1
106 too. The parts for this extended header and footer can be the same
|
| D | TESTING_WITH_SANITIZERS.md | 45 is then the same as in case of gcc, simply add `-Db_sanitize=address,undefined`
46 to the `meson` call and use the same environment variables for runtime configuration.
|
| D | USER_RECORD.md | 200 version of the record on the host, with the same four sections and augmented
221 users with the same name that originate in different organizations or
225 distinct from the same user in the `poettering.hq` realm. User records for the
226 same user name that have different realm fields are considered referring to
275 used when comparing two records of the same user to identify the newer one, and
633 is authorized to access the account. The strings should follow the same format
644 private key found on the same token. The resulting decrypted key is then
649 a matching one in `pkcs11TokenUri` and vice versa, with the same URI, appearing
650 in the same order, but this should not be required by applications processing
665 and `clientPin` booleans map to the FIDO2 concepts of the same name and encode
[all …]
|
| /systemd-251/src/basic/ |
| D | filesystems-gperf.gperf | 58 # ext2 + ext3 + ext4 use the same magic
64 # fuseblk is so closely related to fuse that it shares the same magic
83 # nfs is the old version of nfs4, and they share the same magic
118 # note that devtmpfs shares the same magic with tmpfs, given it is just a special named instance of…
124 # note that msdos shares the same magic (and is the older version)
|
| /systemd-251/test/fuzz/fuzz-udev-rules/ |
| D | 60-persistent-storage-tape.rules | 12 # iSCSI devices from the same host have all the same ID_SERIAL,
|
| /systemd-251/rules.d/ |
| D | 60-persistent-storage-tape.rules | 12 # iSCSI devices from the same host have all the same ID_SERIAL,
|
| /systemd-251/src/resolve/ |
| D | resolved-dns-question.c | 219 bool same = true; in dns_question_cname_redirect() local
252 same = false; in dns_question_cname_redirect()
258 if (same) { in dns_question_cname_redirect()
|
| /systemd-251/shell-completion/zsh/ |
| D | _systemd-run | 4 # @todo _systemctl has a helper with the same name, so we must redefine
63 {-d,--same-dir}'[Run on the current working directory]' \
|
| /systemd-251/.semaphore/ |
| D | semaphore.yml | 12 # Cancel any running or queued job for the same ref
|
| /systemd-251/test/ |
| D | README.testsuite | 4 The same image is used for execution under `systemd-nspawn` and `qemu`.
142 reachable in the same URL parent directory as the logs.gz that gets linked on
174 the same Ubuntu release as is used by Ubuntu CI (Focal ATTOW).
258 And then execute it in the same way as above:
|
| /systemd-251/src/locale/ |
| D | meson.build | 20 # If you know a way that allows the same variables to be used
|
| /systemd-251/src/home/ |
| D | homed-manager.c | 677 bool same; in manager_add_home_by_image() local
684 same = user_record_storage(h->record) == storage; in manager_add_home_by_image()
685 if (same) { in manager_add_home_by_image()
687 same = path_equal(h->sysfs, sysfs); in manager_add_home_by_image()
689 same = false; in manager_add_home_by_image()
694 same = p && path_equal(p, image_path); in manager_add_home_by_image()
698 if (!same) { in manager_add_home_by_image()
|
| /systemd-251/ |
| D | .lgtm.yml | 11 - include: cpp/nested-loops-with-same-variable
|