Re: RFC: OpenRC as Init System for Debian
On Tue, May 15, 2012 at 5:38 PM, Stefan Fritsch <firstname.lastname@example.org> wrote:
> On Wednesday 09 May 2012, Gergely Nagy wrote:
>> > Apart from the fact that requirements will be different on
>> > different systems. Putting functionality for all possible corner
>> > cases into the daemon is not sensible for any upstream.
>> That is what configuration files and similar things are for, I
>> I'd love to see an example where a complex init script is needed,
>> and that can't be easily turned into systemd service files (for
>> example). So far, I was told of two cases where the init script
>> does more than a simple unit file does: one was nbd-client, which
>> does funky stuff I dared not try to understand last night, the
>> other is every package that supports starting multiple instances
>> of the same service.
> For example, the apache2 init script starts htcacheclean if and only
> if mod_disk_cache is enabled. While this could arguably be considered
> as an upstrem deficiency, such cases won't simply disappear because
> systemd becomes more common. And fixing this in the daemon as part of
> a packager's work is not feasible. And with my upstream hat on, I
> would rather spend my time on fixing real bugs than things that can be
> easily worked around by the init script (or the apachectl script).
> Also, the apache2 init script creates various required directories on
> volatile file systems like /var/run or /var/lock
Move this logic out of the init script and use ExecStartPre? That way
the same logic can be used by all init systems.
Please read systemd.service(5) if you haven't already.
> and supports multiple
> running instances, but these are more common problems.
As far as I can tell, systemd supports multiple instances natively...