https://bugzilla.novell.com/show_bug.cgi?id=821879 https://bugzilla.novell.com/show_bug.cgi?id=821879#c54 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mt@suse.com |fcrozat@suse.com --- Comment #54 from Marius Tomaschewski <mt@suse.com> 2013-07-11 12:01:53 UTC --- (In reply to comment #51)
for me, systemctl (and systemd) are ok:
main process (ie /etc/init.d/network, on the Process line) was executed, finished and returned an exit code of 0 => Active (because /etc/init.d/network has X-Systemd-RemainAfterExit: true) and Exited because the pid referenced on the Process line is no longer running
there is still one process running, which was started by this process, and it is dhcpcd.
And why does it behaves like this only in 50% of the cases/boots [when VM is on tmpfs of a fast host, VM on HDD in <10% of the cases]? Usually it reports "active (running)" here. Also after "systemctl restart network.service" after it initially booted in "active (exited)" state. The situation is exactly same: rcnetwork exited with status 0, but there is still dhcpcd running. Just the systemd state differs from time to time. And why does systemd -- while udev update -- drops all state and kills all cgroup members (dhcpcd) in "active (exited)" state [run1], but not in the "active (running)" [run3], where it does not kill all network.service cgroup members? => See run1 and run3 in the attachment of comment 49. (In reply to comment #52)
Re-assigning the bug to Marius, don't really see this as a udev issue.
It is not a network scripts bug. Network works, 0 status is reported. Re-assigning to Frederic as systemd is not consistent / behaves strange. -- 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.