Your message dated Tue, 2 Aug 2016 07:33:18 +0200 with message-id <[email protected]> and subject line Re: Bug#833185: Udhcd not killed when DHCP_ENABLED is no has caused the Debian Bug report #833185, regarding Udhcd not killed when DHCP_ENABLED is no to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 833185: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833185 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: udhcpd Version: 1:1.22.0-9+deb8u1 Severity: minor Udhcpd is running. I edit /etc/default/udhcpd to set DHCPD_ENABLED to no, then do /etc/init.d/udhcpd stop The scripts checks the value of DHCPD_ENABLED, and does nothing. Is this the expected behaviour? Shouldn't the stop action kill a running udhcpcd unconditionally? -- Juliusz
--- End Message ---
--- Begin Message ---On Mon, Aug 01, 2016 at 11:48:38PM +0200, Juliusz Chroboczek wrote: > > Udhcpd is running. I edit /etc/default/udhcpd to set DHCPD_ENABLED to no, > then do > > /etc/init.d/udhcpd stop > > The scripts checks the value of DHCPD_ENABLED, and does nothing. > > Is this the expected behaviour? Yes. > Shouldn't the stop action kill a running udhcpcd unconditionally? It does when DHCPD_ENABLED. Script /etc/init.d/udhcpd begins with sourcing /etc/default/udhcpd and see that way is it disabled and exits. Works fine at start up. Works fine at stop when udhcpd was stopped before /etc/default/udhcpd was edited. Groeten Geert Stappers -- Leven en laten leven
--- End Message ---
