[systemd-devel] systemd "hangs" for several minutes on shutdown if it gets "service force-reload" request
Tomasz Torcz
tomek at pipebreaker.pl
Mon Jan 17 00:39:28 PST 2011
On Fri, Jan 14, 2011 at 12:44:46PM +0100, Tollef Fog Heen wrote:
> ]] Tomasz Torcz
>
> Hi,
>
> | “ SIGUSR2
> | When this signal is received the systemd manager will log its complete
> | state in human readable form. The data logged is the same as printed by systemctl dump.
> | ”
>
> This is useful. It'd be even more useful if I could just hit a key
> combination and make it happen. Do you know if I can?
There kbrequest.target which is started when systemd receives SIGWINCH or
you press Alt+↑ on console. I suppose you could drop and enable following
unit:
---
[Service]
ExecStart=/bin/systemctl list-jobs
StandardOutput=tty
[Install]
WantedBy=kbrequest.target
---
and “systemctl enable …” it. Now pressing alt-up during boot should show
you what jobs systemd is waiting for. Likewise, you can change ExecStart= to
“/bin/kill -USR2 1” (or “/bin/systemctl dump”) to have full dump. But
full dump is probably less useful.
--
Tomasz Torcz ,,If you try to upissue this patchset I shall be seeking
xmpp: zdzichubg at chrome.pl an IP-routable hand grenade.'' -- Andrew Morton (LKML)
More information about the systemd-devel
mailing list