Am 15.12.2011 08:49, schrieb T.C. Hollingsworth:
On Wed, Dec 14, 2011 at 6:48 PM, Reindl Harald
<h.reindl(a)thelounge.net> wrote:
> 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
Services are supposed to be shutdown in the reverse order of their
Before/After dependencies
that was my idea for this "fake-service"
so this sounds like a bug in SysV compat to me.
sounds reasonable
At any rate, you should be able to work around this by setting in
[Service] "SysVStartPriority=90" (or any value higher than vmware's
start priority)
thanks, i will give it a try and feedback ASAP
currently RAID-check is running :-)