m (debug-shell word) |
m (unbold) |
||
Line 18: | Line 18: | ||
or a combination of those for example. Those will limit the processes being launched by '''systemd'''. | or a combination of those for example. Those will limit the processes being launched by '''systemd'''. | ||
{{admon/warning|Use the debug-shell only while actually debugging!|Do not forget to disable debug-shell.service after you've finished debugging your boot problems. Leaving the root debug-shell always available would be a security risk since anybody in presence could just press '''Ctrl+Alt+F9''' to obtain root privilege.}} | {{admon/warning|Use the debug-shell only while actually debugging!|Do not forget to disable '''debug-shell.service''' after you've finished debugging your boot problems. Leaving the root debug-shell always available would be a security risk since anybody in presence could just press '''Ctrl+Alt+F9''' to obtain root privilege.}} |
Revision as of 08:17, 4 June 2021
enable debug-shell for Ctrl-Alt-F9
In case of e.g. boot-time problems with systemd, it is useful to have as root a debug-shell early available. CTRL+ALT+F9 will immediately switch to the debug-shell ("bash") without prompting for the password, saving precious time.
- Enable using
systemctl enable debug-shell
- Next time after booting, you will be able to switch to tty9 by pressing the 3 key combo CTRL+ALT+F9 and have a bash debug-shell available from an early stage in the booting process.
Use the debug-shell e.g. for checking the status of services, reading logs, looking for stuck jobs with systemctl list-jobs
, htop , killall etc..
- When done, disable with
systemctl disable debug-shell
to keep others from obtaining passwordless root access. - You may also want to consider alternative troubleshooting techniques available as kernel parameters. Edit e.g. GRUB2 vmlinuz line, adding
debug rescue emergency 1
or a combination of those for example. Those will limit the processes being launched by systemd.