On Wed, Sep 5, 2012 at 4:51 PM, Cristian Rodríguez <crrodriguez@opensuse.org> 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. if there is no particular process to talk, then the application is unmanaged, uncontained and may do whatever it pleases.
And there, Andreas, as I was saying, the whole problem lies. 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". Then, threads read like: There's a problem here. NOT SO YES SO NOT SO DUH STOP IT YOU STOP IT Quite unproductive. Were it some inconsequential application, I wouldn't care. But it's a core system component the one we're talking about here. It's good to know Frederic is pushing solutions and convincing upstream, though from what I've read on the internet, systemd upstream's attitude is pretty much like Cristian's. Next thing you know, they'll push binary logs on us. <--- flaming forbidden -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org