The https://bugzilla.novell.com/show_bug.cgi?id=830675 describes a problem where vbox initscript apparently stopped working under systemd. Script is supposed to start VMs on system boot. As long as I can tell, script actually does work - but when it finishes, systemd interprets it as service has finished and starts ExecStop script which in this case stops VMs again:
jul 26 18:30:08 linux-mh9j systemd[1]: Child 11556 died (code=exited, status=0/SUCCESS) jul 26 18:30:08 linux-mh9j systemd[1]: Child 11556 belongs to vboxes.service jul 26 18:30:08 linux-mh9j systemd[1]: vboxes.service: control process exited, code=exited status=0 jul 26 18:30:08 linux-mh9j systemd[1]: vboxes.service got final SIGCHLD for state start jul 26 18:30:08 linux-mh9j systemd[1]: About to execute: /etc/init.d/vboxes stop ... jul 26 18:30:08 linux-mh9j vboxes[11580]: Shutting down Virtualbox machines: suse_12.3 (user: root) ... I do not see this behavior actually documented anywhere so my question is - is it intentional? This is openSUSE 12.3 with systemd 195. P.S. note proper unit will lose very useful functionality - actual status output of running VMs. Any news about ExecStatus support? _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
