On 06/15/2012 04:35 PM, Bill Nottingham wrote:
Another advantage of the split is that maintainers do not get the temptation to just copy their whole old SysV initscript as /usr/lib/initscripts/legacy-actions/<service>.
That's exactly what I would encourage for simplicity's sake - why do you think this is a bad idea? Simply because it would encourage accidental overriding of start/stop/restart, etc.?
Yes, I worry about accidental overriding. And about careless preservation of everything that was in the SysV scripts. I want the packagers to think about each custom action they add and contemplate whether the action is really needed.
I mean the problem with providing a single script for legacy actions is the above - you need to do some hacks to pass those to a single script while still falling back to systemctl for generic actions.
Right. It would require the service script to have a list of the generic actions that systemctl understands. The split action scripts make this problem simpler.
Michal