Bug#826012: /lib/lsb/init-functions.d/40-systemd: Support for compound target units as first-order services

2024-05-26 Thread Luca Boccassi
Control: tags -1 wontfix Control: close -1 On Mon, 10 Dec 2018 14:21:33 +0100 Michael Biebl 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.ta

Bug#826012: /lib/lsb/init-functions.d/40-systemd: Support for compound target units as first-order services

2018-12-10 Thread Michael Biebl
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 a

Bug#826012: /lib/lsb/init-functions.d/40-systemd: Support for compound target units as first-order services

2018-12-10 Thread Michael Biebl
Hi Am 01.06.16 um 14:07 schrieb Terry Burton: > This message [1] identifies that compound target units are the > appropriate mechanism for controlling multiple service units. > > The LSB override hook currently only consider .service units, ignoring > compound .target units. > > Support for this

Bug#826012: /lib/lsb/init-functions.d/40-systemd: Support for compound target units as first-order services

2016-06-01 Thread Terry Burton
Package: systemd Version: 230-2 Severity: normal This message [1] identifies that compound target units are the appropriate mechanism for controlling multiple service units. The LSB override hook currently only consider .service units, ignoring compound .target units. Support for this would be u