1SYSTEMD-DEBUG-GENERATOR(8) systemd-debug-generator SYSTEMD-DEBUG-GENERATOR(8)
2
3
4
6 systemd-debug-generator - Generator for enabling a runtime debug shell
7 and masking specific units at boot
8
10 /usr/lib/systemd/system-generators/systemd-debug-generator
11
13 systemd-debug-generator is a generator that reads the kernel command
14 line and understands three options:
15
16 If the systemd.mask= or rd.systemd.mask= option is specified and
17 followed by a unit name, this unit is masked for the runtime (i.e. for
18 this session — from boot to shutdown), similarly to the effect of
19 systemctl(1)'s mask command. This is useful to boot with certain units
20 removed from the initial boot transaction for debugging system startup.
21 May be specified more than once. rd.systemd.mask= is honored only by
22 initial RAM disk (initrd) while systemd.mask= is honored only in the
23 main system.
24
25 If the systemd.wants= or rd.systemd.wants= option is specified and
26 followed by a unit name, a start job for this unit is added to the
27 initial transaction. This is useful to start one or more additional
28 units at boot. May be specified more than once. rd.systemd.wants= is
29 honored only by initial RAM disk (initrd) while systemd.wants= is
30 honored only in the main system.
31
32 If the systemd.debug_shell or rd.systemd.debug_shell option is
33 specified, the debug shell service "debug-shell.service" is pulled into
34 the boot transaction and a debug shell will be spawned during early
35 boot. By default, /dev/tty9 is used, but a specific tty can also be
36 set, either with or without the /dev/ prefix. Note that the shell may
37 also be turned on persistently by enabling it with systemctl(1)'s
38 enable command. rd.systemd.debug_shell= is honored only by initial RAM
39 disk (initrd) while systemd.debug_shell is honored only in the main
40 system.
41
42 systemd-debug-generator implements systemd.generator(7).
43
45 systemd(1), systemctl(1), kernel-command-line(7)
46
47
48
49systemd 253 SYSTEMD-DEBUG-GENERATOR(8)