В Sun, 15 Dec 2013 23:23:54 +0100 Lennart Poettering <lenn...@poettering.net> пишет:
> > This is really not how we should do it: the admin must be capable of > tracing and pausing the boot process, and an init system should not make > that impossible. > What happens currently when service gets SIGSTOP? Does systemd ignore it? Will it reflect this information in service state? Actually, what state service *is* in this case (it obviously is not running but is not failed either ...)? _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
