On Tue, Aug 23, 2011 at 9:19 AM, Lennart Poettering
<mzerqung(a)0pointer.de> wrote:
So the daemon listens on a local socket. That means it's quite
important
that systemd waits with starting the next service until your daemon
finished starting up (and hence finished establishing the listening
socket), so that the next service can rely that the listening socket is
connectable. That means Type=forking is a working choice.
In all cases using socket activation is preferable since it increases
parallelization, robustness and simplicity, but this requires patching,
as mentioned.
I verified it does create a PID file in /var/run so that looks like the winner.
Thanks for the help!
Richard