Home
last modified time | relevance | path

Searched refs:handled (Results 1 – 6 of 6) sorted by relevance

/systemd-251/src/pstore/
Dpstore.c97 bool handled; member
125 if (pe->handled) in move_file()
170 pe->handled = true; in move_file()
224 if (pe->handled) in process_dmesg_files()
357 .handled = false, in list_files()
/systemd-251/docs/
DBOOT_LOADER_SPECIFICATION.md134 was traditionally handled), all installed OS share the same place to drop in
431 previous boot loader logic was largely handled by in distribution-specific
DUSER_GROUP_API.md141 NSS (and not natively via Varlink) are handled by the
DUIDS-GIDS.md285 Note that the range 2147483648…4294967294 (i.e. 2^31…2^32-2) should be handled
/systemd-251/hwdb.d/
D60-keyboard.hwdb313 …KEYBOARD_KEY_88=unknown # Fn+F2 Turn On/Off Wireless - handled in h…
380 KEYBOARD_KEY_88=unknown # Fn-PrtScr rfkill - handled in HW
2012 # (KEYBOARD_LED_CAPSLOCK) are currently handled and need their values set
/systemd-251/
DNEWS964 and how the delegated prefixes are handled by the DHCPv6 client.
2572 accessing the device should then be handled gracefully.
2624 systemd's own configuration is handled. Given that PAM stack
2811 useful in cases where multiple errors shall be handled the same way.
4496 be handled the same way as watchdog events.
4840 and IPv4LL addresses. The way that devices that were handled
8069 to be handled.
10743 directory closer in line with how IPC objects are handled.