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 -- Dirk Heinrichs <dirk.heinri...@altum.de> GPG Public Key: D01B367761B0F7CE6E6D81AAD5A2E54246986015 Sichere Internetkommunikation: http://www.retroshare.org Privacy Handbuch: https://www.privacy-handbuch.de
signature.asc
Description: OpenPGP digital signature
