Le jeudi 06 septembre 2012 à 01:57 +0200, Joachim Schrod a écrit :
Cristian Rodríguez wrote:
The systemd proponents on this list responded "then this is no service". The systemv proponents told them "but it was before". Several small shouting wars started. (Well, not a real flamewar, not like the r.a.sf-lovers split, back in 1991. :-))
That's correct, controlling VMs directly with sysvinit do not really work either, it would seem to work though.
That's not true.
For example, the VMware command "vmrun list" very much gives the list of running VMs to shut down, reliably. And it does so without a controlling process.
I have several applications where one can asks on sockets which ones and how many are running. Without any controlling process. Similar use case.
I'm reading a lot in this thread about vmware and the fact systemd is
broken regarding vmware initscript but I have yet to understand in what
regard it is broken.
Could you enlighten me a little more by giving test case ? Are you
talking about "ExecStatus" (or equivalent in initscript) or of something
else ?
--
Frederic Crozat