Bug#826012: /lib/lsb/init-functions.d/40-systemd: Support for compound target units as first-order services
Luca Boccassi
bluca at debian.org
Sun May 26 14:46:00 BST 2024
Control: tags -1 wontfix
Control: close -1
On Mon, 10 Dec 2018 14:21:33 +0100 Michael Biebl <biebl at debian.org>
wrote:
> Am 10.12.18 um 14:12 schrieb Michael Biebl:
> > Say you have test.service and test.target.
> > I'm not sure if there is a reliable way to detect whether the user
> > wanted test.service or test.target when running "/etc/init.d/test
..."
>
> Just tested systemctl. If you have a test.service and test.target and
> you run
> systemctl start test
> then test.service is started but not test.target.
>
>
> So, I guess what would be more in line with the systemctl behaviour
is a
> patch which does the following:
>
> If you run /etc/init.d/test start:
> - We start test.service if it exists
> - If test.service does not exist and a test.target exist, start the
target.
> - If no service and target exists, fall through and let the sysv init
> script handle the request directly
It's been 6 years since the last update, and the sysv wrappers are on
the way out, so this will become moot soon. Closing.
--
Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20240526/64331f37/attachment.sig>
More information about the Pkg-systemd-maintainers
mailing list