https://bugzilla.novell.com/show_bug.cgi?id=737636
https://bugzilla.novell.com/show_bug.cgi?id=737636#c14
--- Comment #14 from Marius Tomaschewski 2012-02-06 16:41:25 UTC ---
We've added the "X-Systemd-RemainAfterExit: true" support to systemd
and added the flag to the LSB tags in network script to keep services,
that do not have any daemon, in "running" state instead to assume that
they're gone when there is no process after start.
[systemd update is released, sysconfig still in comment 8 repo]
But it seems, there is still some check for empty cgroup somewhere in
systemd causing systemd to execute the stop action for the service:
[ 19.199283] systemd[1]: Accepted connection on private bus.
[ 19.200140] systemd[1]: Got D-Bus request:
org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 19.200235] systemd[1]: network.service: cgroup is empty
[ 19.200344] systemd[1]: About to execute: /etc/init.d/network stop
[ 19.205247] systemd[1]: Forked /etc/init.d/network as 1258
[ 19.205481] systemd[1]: network.service changed running -> stop
See also deadlock problem in bug 724777 comment 4.
Further, AFAIS systemd never calls the "network status" action but always
the cached "start" return code only [that may have reported "in background"
when dhcp didn't get any lease yet, ipv6 dad is not finished yet, ...].
And because "status" isn't always correct, another action results may be
wrong too (e.g. "try-restart").
I were unable to catch the problem until now, because it works for me as
soon as I enable debugging :-/ what is usually a timing/locking problem.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.