If we supported PIDFile= for Type=simple, daemons could drop a PID
file to indicate startup completion without having to be full-on
Type=forking.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
'Twas brillig, and David Timothy Strauss at 16/12/13 08:04 did gyre and
gimble:
If we supported PIDFile= for Type=simple, daemons could drop a PID
file to indicate startup completion without having to be full-on
Type=forking.
Yeah but pidfile is kinda ugly too and has problem when processes
On Mon, 16.12.13 00:04, David Timothy Strauss (da...@davidstrauss.net) wrote:
If we supported PIDFile= for Type=simple, daemons could drop a PID
file to indicate startup completion without having to be full-on
Type=forking.
There has been a TODO list item for a long time to introduce
В 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
On Mon, 16.12.13 06:55, Andrey Borzenkov (arvidj...@gmail.com) wrote:
В 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
On Sat, Dec 14, 2013 at 11:19 PM, Shawn Landden sh...@churchofgit.com wrote:
It would be nice if systemd could implement the service supervisor
side of the service readiness protocol that upstart calls expect
stop:
The service doesn't fork, and when considers itself ready it raises
SIGSTOP.
