Hi folks,
yesterday I reported bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757711, but failed to
let the BTS properly report to this list.
It is basically about the DHCP client terminating directly after network
detection (after receiving signal 15), which interferes later with the
retitle 757711 netcfg: promptly kills dhclient, deconfigures interface
reassign 757711 src:netcfg
found 757711 netcfg/1.118
severity 757711 grave
user debian-bsd@lists.debian.org
usertags 757711 + kfreebsd
thanks
Hi,
On 11/08/14 08:18, Jan Henke wrote:
[...] DHCP client terminating directly
Steven Chamberlain ste...@pyro.eu.org (2014-08-11):
retitle 757711 netcfg: promptly kills dhclient, deconfigures interface
reassign 757711 src:netcfg
found 757711 netcfg/1.118
severity 757711 grave
user debian-bsd@lists.debian.org
usertags 757711 + kfreebsd
thanks
Steve, if you want to
Control: found -1 netcfg/1.117
Cyril Brulebois k...@debian.org (2014-08-11):
Steven Chamberlain ste...@pyro.eu.org (2014-08-11):
retitle 757711 netcfg: promptly kills dhclient, deconfigures interface
reassign 757711 src:netcfg
found 757711 netcfg/1.118
severity 757711 grave
Eeww, I
AFAICT so far:
* netcfg kills the running DHCP client after a hostname is set - this
could be a bug
* on kFreeBSD, isc-dhcp-client-udeb is used; killing it releases the
DHCP lease and deconfigures the interface, which could be intentional
* on Linux, Busybox udhcpc is used, killing it seems to
Steven Chamberlain ste...@pyro.eu.org (2014-08-12):
found 757711 1.108+deb7u1
thanks
On 11/08/14 23:57, Cyril Brulebois wrote:
found 757711 netcfg/1.118
severity 757711 grave
Eeww, I missed that.
Sorry, assumed you'd seen this... though I did feel the severity was
justified
I hope someone can explain the intent of the code below from netcfg:
why are DHCP clients killed here? Is it to avoid them clobbering a
manual hostname/domain setting? And is that really an issue in
practice, with whatever DHCP client[s] we use now?
The other thing is, the whole idea of DHCP is
7 matches
Mail list logo
