On Mon, Apr 8, 2013 at 4:37 PM, Cristian Rodríguez <crrodriguez@opensuse.org> wrote:
On 04/08/2013 04:11 PM, Claudio Freire wrote:
Currently service much more than "running", "stopped".. the can be activated (and stopped) in a variety of ways.
Not sure what you mean here.
I mean that the system no longer works the way rcxxx will produce meaninful output in many cases, many services will start on-demand, udev or desktop environments will ask for them when needed and will be garbage collected when unused.
There are oneshot services on which started/running/stopped does not make sense or static ones where any of those operations may not yield any meaning either.
I don't think that any of that matters for this conversation. Rc scripts handle all those kinds of services, because rc scripts are tailored to the service, and options are added to them besides the standard start/stop. That's one point of rc scripts. They're the epitome of flexibility, even when that comes with a maintainership cost. But it's not the point I was trying to make. Systemd has lots of holes understanding many of those kinds of services that don't just start/stop. Many of them that I've seen wrongfully treated as one-shot services, which is wrong, but nevertheless that doesn't mean systemd can't or shouldn't be taught about them. No, my point wasn't about the service execution model, although I have mentioned the service execution model when ranting against systemd before. My point this time was that there are lots of tasks related to services that don't pertain to starting or stopping them, and there's no hope of adding those to systemctl since they're so varied, nor would it be correct, and this is where rc scripts shine. They act as a central hub to general service administration, and it's good to have such a hub. It eases the sysadmin's task. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org