Re: isc-dhcp-server
Marc Haber <[email protected]> Thu, 30 Jul 2026 08:02:28 +0200
| Newsgroups | comp.os.linux.misc |
|---|---|
| Organization | private site, see http://www.zugschlus.de/ for details |
| Message-ID | <[email protected]> |
Lawrence D´Oliveiro <[email protected]> wrote: >After a Debian Unstable upgrade a couple of months ago, dhcpd (from >the isc-dhcp-server package) would no longer start automatically. This >is because it relies on a sysvinit startup script, and systemd has >finally removed support for that. yes. >Looks like upstream development of that project has largely ceased, "largely ceased" means "deprecated ten years ago, declared EOL three years ago". Upstream. > in >favour of a more elaborate successor that I am in no hurry to switch >to, for my simple home-internal needs. You can switch to something simpler such as dnsmasq or systemd-networkd. But you should not continue running ISC DHCP, that's dead software. You can actually manually >launch /usr/sbin/dhcpd as root and it will automatically fork a daemon >process, but this got a bit tiresome. So I created a systemd service >definition for it: > > [Unit] > Description=ISC DHCP Server > > [Install] > WantedBy=network.target > > [Service] > Type=forking > ExecStart=/usr/sbin/dhcpd > TimeoutStopSec=5 > Restart=always > >That’s just under a dozen lines, including blank ones -- not a bad >replacement for a sysvinit script that is nearly 200 lines in size ... That's what I have always said about systemd units compared to initscript. You could use Type=simple and instruct the daemon to run in foreground for a bit more of control. Self-forking daemons are no longer needed. Greetings Marc -- ---------------------------------------------------------------------------- Marc Haber | " Questions are the | Mailadresse im Header Rhein-Neckar, DE | Beginning of Wisdom " | Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 6224 1600402