Harald Hoyer wrote:
On 06/18/2009 09:32 AM, Seewer Philippe wrote:
Warren Togami wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=506626
Filed the dhclient segfault here. I've been trying to debug this for
the past 5 hours straight. I'm perplexed.
Backing out to 1a945a576c0016c47f983d27727443ac33c5b6a8 prior to
Phillippe's patch series dhclient does not crash.
That is weird. I have no problems at all with isc-dhclient-V3.1.1
Question: Does it segfault in the test-suites as well?
WORKSFORME
fine with: dhclient-4.1.0-20.fc11.x86_64
I've not been able to reproduce the segfault.
But I've got the dhcp decline in vanilla isc dhclient-4.1.
Apparently dhclient-4.1 calls the dhclient-script twice with
reason BOUND. I have no idea why. But my dhclient-script has
(sadly) a small bug, which causes the dhclient to loop
endlessly and dhclient always declining.
Patch below fixes this, but I have absolutely no idea why.
diff --git a/modules.d/40network/dhclient-script b/modules.d/40network/dhclient-script
index 80ab54c..4153eb8 100755
--- a/modules.d/40network/dhclient-script
+++ b/modules.d/40network/dhclient-script
@@ -43,12 +43,12 @@ if getarg rdnetdebug ; then
set -x
fi
-# Huh? Interface configured?
-[ -f "/tmp/net.$netif.up" ] && exit 0
-
# We already need a set netif here
netif=$interface
+# Huh? Interface configured?
+[ -f "/tmp/net.$netif.up" ] && exit 0
+
case $reason in
PREINIT)
ip link set $netif up
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
