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

[Michael Stapelberg]

Hi Apollon,

Apollon Oikonomopoulos <apoikos at debian.org> writes:
> was loaded but not enabled. Unfortunately the semantics of TriggeredBy 
> seem to be poorly documented. Anyway, I will submit a more elegant 
> version :)
Cool. Also note that patches with documentation updates/clarifications
are appreciated on the systemd-devel list.

> I think all three paths should exhibit the same behavior, ideally 
> without code duplication. Two ways come into mind:
>
>  • Provide a "module" with generic and reusable shell functions in the 
>    systemd package, that will offer high-level behaviour, e.g. "handle 
>    service start if systemd is running".
>
>  • Convince upstream to add a new higher-level systemctl subcommand that 
>    will start/stop a unit together with all its triggering units.
Both ways require a new version of systemd to be uploaded to Debian, so
none has a pragmatic advantage. I think it’d be worthwhile to attempt #2
first and fall back to #1 if upstream doesn’t want such a command.

-- 
Best regards,
Michael