[Pkg-systemd-maintainers] Bug#734848: Bug#734848: systemd: LSB initscript wrappers should also handle sockets on start/stop

[Michael Stapelberg]

Hi Apollon,

Apollon Oikonomopoulos <apoikos at gmail.com> writes:
> Currently the wrappers in /lib/lsb/init-functions.d/40-systemd will wrap
> starting/stopping any service with a corresponding systemd service unit 
> file in a systemctl call. This works well with most services, however if 
> a service supports socket activation and ships a socket unit, the socket 
> will not be started/stopped during these operations.
>
> In the case of stop, this means that the service is not effectively
> stopped, but instead restarted, since it will be re-activated on the next
> connection. This is especially important for administrators, who tend to use
> /etc/init.d/<service> either directly or through scripts and expect the service
> to be permanently stopped after the stop action.
>
> Although there are unit-side workarounds for this (e.g. adding PartOf=
> to the socket unit definition), IMHO the desired behavior would be to
> detect if the service has a corresponding socket enabled, and start/stop
> this as well. For the record, this is also the behavior currently
> implemented by service(8) (which also checks that the socket actually
> triggers the given service).
Agreed. If you want to accelerate things, please attach a patch. Also,
FYI, I won’t work on this until #727708 is resolved.

-- 
Best regards,
Michael