On Sat, Sep 21, 2013 at 07:50:22PM +0200, Michael Stapelberg wrote:
> Bastian Blank <wa...@debian.org> writes:
> > On Sat, Sep 21, 2013 at 06:45:41PM +0200, Michael Stapelberg wrote:
> >> sysvinit scripts that many of our current packages provide. However,
> >> when a package ships a native systemd service file in addition to the
> >> sysvinit script, users enjoy a couple of advantages: they can now easily
> >> enable/disable the service in a consistent manner using “systemctl
> >> enable”, daemon output is stored in the journal by default, the process
> >> tracking and related error reporting works better and users can use
> >> drop-in snippets to tweak service behavior (e.g. resource limits).
> >
> > Can you please explain what does not work if the sysv compatibility is
> > used? systemd internally defines a complete service definition for each
> > enabled sysv init script.
> I didn’t say that things _dont_ work at all, I am saying that a few
> details work better when providing a service file:
By describing what works now you implied that it did not work before.
Please update the proposal text to only list new supported stuff.
> • The drop-in snippets I mentioned above (i.e. files like
> /etc/systemd/system/apache2.service.d/more-memory.conf) only work with
> native service files AFAIK,
Can you please actually test this?
Bastian
--
The best diplomat I know is a fully activated phaser bank.
-- Scotty
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130921182549.gb23...@mail.waldi.eu.org
