On Sun, 10 May 2020 15:07:06 +0200 Dirk Heinrichs <dirk.heinri...@altum.de> wrote: > Hi, > > I wonder why these two bugs are considered blockers for this one? From > the 3 scenarios below > > * DHCPv4 only > * DHCPv6 only > * DHCPv4 and DHCPv6 > > only the last one would need to have both started, so only this _might_ > have a use for compound target units. But even if they are not > available, one can still enable/start each service separately via its > own service file. This means that 826011 and 826012 are, at most, nice > to have, but in no way are they blocking systemd service files for > isc-dhcp-server, right? > > In addition, the current init script based mechanism for running both is > also buggy: When one service got killed, its PID file is still around, > which results in the init script refusing to start ANY of them unless > that PID file is removed. > > So, please, replace the current init script with proper, independent > systemd service files for both dhcpdv4 and dhcpdv6 for bullseye. A > compound target unit can still be added later. > > Bye... > > Dirk
Ping - any update on this? It would be good to get this sorted as mentioned above. isc-dhcp is one of the few popular packages left without native units. -- Kind regards, Luca Boccassi
signature.asc
Description: This is a digitally signed message part
