On 04/08/2013 02:33 PM, Claudio Freire wrote:
On Mon, Apr 8, 2013 at 2:04 PM, Frederic Crozat
wrote: - rcxxx symlinks were not part of sysvinit, it is yet another SUSE extension.
Yes and we should carry it, because many of our users are still using it. Removing it just for the sake of removing it is absurd.
Not only that, rc scripts, when scripts and not just symlinks,
As far as I am concerned is just a bunch of confusing unnecesary hacks that people apparently have an emotional attachment to. Currently service much more than "running", "stopped".. the can be activated (and stopped) in a variety of ways. provide
a much-needed standardized way of getting to figure out the "extended status" of some services. Init scripts provided them when SysVinit was the only way, but I agree pegging extra functionality into SysVinit scripts was... dubious. However, having rc scripts provide said extra functionality makes a lot of sense.
What do you mean ? systemctl does report the service status..
And by extended status I mean something beyond systemd's "yeah, I started it - it ought to be running". Just try rcapparmor status on 12.2 to see how useless asking systemctl is.
apparmor has to be hooked up to systemd the same way they other LSMs already are, nobody has done the required work though (unlike redhat or intel that paid people to do the work upstream) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org