Home
last modified time | relevance | path

Searched refs:subsystems (Results 1 – 18 of 18) sorted by relevance

/systemd-251/src/libsystemd/sd-device/
Dtest-sd-device.c254 _cleanup_(hashmap_freep) Hashmap *subsystems; in TEST()
260 assert_se(subsystems = hashmap_new(&string_hash_ops)); in TEST()
277 h = hashmap_get(subsystems, subsystem); in TEST()
282 assert_se(hashmap_put(subsystems, str, h) >= 0); in TEST()
291 while ((h = hashmap_steal_first_key_and_value(subsystems, (void**) &s))) { in TEST()
/systemd-251/src/udev/
Dudevadm-trigger.c423 _cleanup_strv_free_ char **subsystems = NULL; in trigger_main() local
425 subsystems = strv_split(optarg, ","); in trigger_main()
426 if (!subsystems) in trigger_main()
429 STRV_FOREACH(p, subsystems) { in trigger_main()
/systemd-251/docs/
DUSER_GROUP_API.md19 user/group records from local services, and allows local subsystems to provide
81 the various subsystems that want to offer user and group records to the rest of
159 should be implemented in the subsystems that provide the user records, not in
DUSER_NAMES.md15 processing users/group defined by other subsystems and when defining users/groups
98 by these other subsystems.
DBLOCK_DEVICE_LOCKING.md82 between subsystems.
DCOREDUMP_PACKAGE_METADATA.md10 *Intended audience: hackers working on userspace subsystems that create ELF binaries
DUIDS-GIDS.md27 where various subsystems map unmappable users to, for example file systems
144 subsystems allocating from the same ranges it is hence essential that they
DCONTAINER_INTERFACE.md31 systemd and various other subsystems (such as the SELinux userspace) have
326 ownership. Multiple other subsystems of systemd similarly test for `/sys/`
DRANDOM_SEEDS.md19 an API to userspace as well as to internal kernel subsystems to retrieve
92 entropy from various non-hwrng sources in various subsystems, all of which
DTEMPORARY_DIRECTORIES.md87 `systemd-tmpfiles` btw, it's inherited from previous subsystems such as
DUSER_RECORD.md254 by geo-location subsystems, but this is not enforced nor required. Example:
1008 various applications. In general, subsystems are free to introduce their own
DCGROUP_DELEGATION.md10 *Intended audience: hackers working on userspace subsystems that require direct
/systemd-251/shell-completion/bash/
Dudevadm124 comps='all devices subsystems'
/systemd-251/shell-completion/zsh/
D_udevadm27 '--type=[Trigger a specific type of devices.]:types:(all devices subsystems failed)' \
/systemd-251/catalog/
Dsystemd.catalog.in504 guarantees other subsystems traditionally assumed it provides. Relying on this
/systemd-251/hwdb.d/
D70-mouse.hwdb12 # Supported subsystems: usb, bluetooth
Dpci.ids21 # Vendors, devices and subsystems. Please keep sorted.
/systemd-251/
DNEWS377 process certain subsystems (and all their parent devices) earlier.
383 --initialized-nomatch to trigger both subsystems and devices, only
1495 parameters via the credential subsystems. Thus, as above this may be
3040 wrong. Storage subsystems are expected to properly detach their
13905 subsystems.