El 04/09/12 18:37, Joachim Schrod escribió:
Andreas Jaeger wrote:
As far as I know, there's still no integrated solution to the vmware status reporting case (which is incidentally equivalent to a few services I run). Upstream's unwillingness to provide such a simple facility is quite misterious.
What exactly is the vmware status reporting case? Please show an example...
I assume it's the systemd assumption that a service is a running daemon and that the status can be checked by checking on that daemon.
Whereas, the status (and the shutdown) of a virtual machine service means to locate all running VMs and trigger them to shut down. For several VM products, there *is* no controlling process for the VMs. There are several other use cases that have similar properties.
There might be no controlling process, but at least there should be some kind of notification that VM "foo" is going down/up/freeze etc. that's something up the vendor to provide..
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. if there is no particular process to talk, then the application is unmanaged, uncontained and may do whatever it pleases.
When some people (me included) brought that issue up for 12.1, we got shut down -- in particular, I was flamed several times by Christian Rodriguez with him _never_ answering the actual technical question how to approach a solution for this problem.
I am not flaming YOU, at the best I am attacking YOUR IDEAS. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org