https://bugzilla.novell.com/show_bug.cgi?id=821879 https://bugzilla.novell.com/show_bug.cgi?id=821879#c60 --- Comment #60 from Frederic Crozat <fcrozat@suse.com> 2013-07-12 13:27:32 UTC --- (In reply to comment #59)
(In reply to comment #55)
Hmm: - the systemd behavior is inconsistent.
With dhcp: it _usually_ reports correctly "active (running)", _sometimes_ "active (exited)"
You basically need a VM on a tmpfs of a fast host to get the "active (exited)".
Looks to me, that the RemainAfterExit logic is not sufficient or there is some kind of race condition. To 'considers all PID to be potentially "main PID"' is IMO correct.
Systemd should set the state consistently with RemainAfterExit: always "active (running)" when the main PID (of started init script) process exits and cgroup is not empty and when the cgroup becomes empty, change to "active (exited)".
What is the output of systemctl show network.service in both case ?
- Providing a network.service lease has potential to break the service switch in yast2 -- but I didn't tested it.
I don't see how it would break service switch ? -- 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.