On Fri, Jan 16, 2015 at 7:17 PM, Luca Beltrame <lbeltrame@kde.org> wrote:
Yamaban wrote:
For most services / deamons systemd is limiting their functionality, but just enough to get them working for most of the use-cases.
I said, it wasn't meant as flaming, and I got back a rant/flame. No matter what the rant is, "forced" or not, openSUSE supports only systemd. So my question is, and it is a *honest* question (please don't reply with "forced down etc...", it makes discussion on this list even more demotivating than what normally is, and that's a big understatement), why keep init scripts instead of systemd units?
Because they work, and initscripts are a supported method of service description in systemd, that should be reason enough not to make packages fail. IOW, if an rpmlint rule were to be added, it should be with a really low badness. On Fri, Jan 16, 2015 at 7:54 PM, Jan Engelhardt <jengelh@inai.de> wrote:
On Friday 2015-01-16 22:54, Yamaban wrote:
Now, with sysVinit scripts is was easy to go beyond pure 'standard' (start|stop|restart|reload|status) and implement options as-needed. E.g. a clear-cache option for a proxy.
Yeah, see where that got us. That clear-cache command would only be supported on a handful of distributions (hardly more than one). Howto documents would have to explain one different method for every distribution. Remember rcNAME, "start-stop-daemon" and "service". Or "chkconfig" and "insserv"[*]. One available on Debian, the other on Fedora -- or something in that ballpark.
Still, there is a straightforward way to implement such a feature with initscripts. On Fri, Jan 16, 2015 at 7:54 PM, Jan Engelhardt <jengelh@inai.de> wrote:
Now there is a 'replacement' that is forced down our throats, that is NOT clear and easy to understand, that has masses of missing features,
Don't forget all the missing features of sysvinit.
Take a look at AppArmor. I'm not its maintainer, and its maintainer probably will tell a more accurate story, but IMV there's another reason to keep initscripts around: it has been almost 2 years since the idea of ExecStatus (something that would provide some of the missing functionality for AppArmor) was raised, was not blatantly rejected by systemd folks, and yet is yet to reach us. In the meanwhile, systemd has been expanding its reach way beyond what service unit files do, so it's not a lack of manpower. A reason to keep using initscripts thus is that they get more maintenance. Certainly an rpmlint rule cannot hope to evaluate those motives, and they would just add noise to the build. Why bother? The effort is better spent uploading bug reports mentioning the deficiencies on the existing initscripts. If and when the solution to those issues is creating a systemd unit files, then its maintainer will consider it. I don't see a value to adding units for the sake of units. Is there one? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org