Support for legacy init script actions for systemd services
notting at redhat.com
Wed Jun 27 15:29:51 UTC 2012
Tom Lane (tgl at redhat.com) said:
> Bill Nottingham <notting at redhat.com> writes:
> > Better late than never (and thanks to Michal Schmidt), I've added support to
> > /sbin/service for running legacy actions if specified.
> I'm confused. Only 2 months ago I was told that this was firmly
> against policy and I should get rid of code that assumed it worked
> (which, btw, it already did):
> Did that packaging guideline get reverted already?
My reading is that this is completely consistent with that guideline - the
guideline states that the commands must be standalone helper scripts. That's
what this supports - it just creates a standard location and integration
point for those standalone helpers rather than having it completely ad-hoc.
> > For each legacy option (such as "xyzzy") supported by your init script (such
> > as "frobozz"), package an executable script named:
> > /usr/libexec/initscripts/legacy-actions/frobozz/xyzzy
> What do we need to Require: for this? Is there still a requirement to
> hide it in a foo-sysvinit subpackage?
You *could* require a new initscripts version once it's built, but I don't
know that it's entirely needed - it will be pushed for F16/F17/F18, and
initscripts is implicitly in the dependency chain for approximately
No, it wouldn't need subpackaged.
More information about the devel