On Wednesday 30 Apr 2014 23:26:48 Rodrigo Rivas wrote:
Although the original problem has already been solved, I'll post my trick to debug this kind of issues with systemd:
* Before doing the thing that causes the problem run as root `systemctl start debug-shell`. If the problem is in the boot sequence, then run `systemctl enable debug-shell` and then restart. * That unit will open a root shell in TTY9, so beware of the security issues if you let that enabled. This shell will be enabled from the early boot until the final shutdown. * When the system hangs, switch to TTY9, with Alt+F9 or Ctrl+Alt+F9 and get access to the debug shell. There you can run `systemctl list-jobs` or `journalctl -b` to see what is wrong with your system.
Very useful; thank you. I wonder if you might write that up on the Wiki page for systemd? Paul