On Wed, Sep 5, 2012 at 5:41 PM, Cristian Rodríguez <crrodriguez@opensuse.org> wrote:
After expressing a need for controlling VMs at startup/shutdown, the answer is usually on that tone. Ie: "You're wrong, you don't need it, you should ask someone else, stop bothering."... etc. No rationale provided, no alternative way of doing it, no nothing. Just a "NOT SO".
No, I am explaining the current state of things, with or without systemd.
If you are using the libvirt daemon then you can control the VMs,without these kind of "directors" it is impossible for either init systems to control them in anyway other than "start".
It doesn't matter if it's libvirt or libzunga(tm), systemd cannot be expected to have native support for all possible libstuff controlling non-daemons, so it has to support customizable ways of doing everything. Start, stop, and checking status, minimally. It's missing the status one. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org