Am 15.12.2011 02:17, schrieb Olav Vitters:
On Wed, Dec 14, 2011 at 10:18:10AM +0100, Reindl Harald wrote:
> ah sounds exactly what i searched for, thanks
Did systemd log anything in syslog about forcefully shutting down the
service/unit/... because of the timeout? If not, could you file an
enhancement bug with systemd?
it seems that this even does not work with the timeout 100%
normally i would expect that this service is stopped before
"vmware.service" which is a sysvinit, but after some tests
i had still VMs which started the next time with fscheck
while doing this manually and after that reboot there is no
problem
seems like there is some paralleizm at shutdown which is
very very bad - stopping "vmware.service" kills all running
machines since the included suspend worked only with <= F14
frustrating!
[root@srv-rhsoft:~]$ cat /etc/systemd/system/vmware-default.service
[Unit]
Description=VMware-Default-Machines
After=vmware.service
[Service]
Type=oneshot
ExecStart=/bin/su -c "/scripts/vmware/vm-default-start.sh" vmware
ExecStop=/scripts/vmware/vm-suspend-all.sh
RemainAfterExit=yes
TimeoutSec=600
[Install]
WantedBy=multi-user.target