<span style="background-color: transparent; ">Good news and bad news. The good news I have a patch to "/sbin/dhclient-script" that fixes this. The bad news is that is causes /etc/init.d/hostname.sh to fail at boot. To have the hostname be set by dhclient, with this patch, "/etc/hostname" must exist but have a length of zero:</span><div>
<br></div><div><div>--- /sbin/dhclient-script 2011-11-02 16:44:47.000000000 -0400</div><div>+++ /sbin/dhclient-script.bak 2011-08-09 14:50:08.000000000 -0400</div><div>@@ -152,9 +152,9 @@</div><div> ;;</div>
<div> BOUND|RENEW|REBIND|REBOOT)</div><div> </div><div>- if [ ! -s /etc/hostname ]; then</div><div>- # /etc/hostname lenth == 0 set hostname</div><div>- hostname "$new_host_name"</div>
<div>+ if [ -n "$old_host_name" -a -n "$host_name" -a \</div><div>+ "$host_name" != "$old_host_name" ]; then</div><div>+ hostname "$new_host_name"</div>
<div> fi</div><div> </div><div> if [ -n "$old_ip_address" -a -n "$alias_ip_address" -a \</div></div><div><br></div><div><span style="background-color: transparent; ">The hostname.sh issue isn't critical, but it's still a bit unsettling to see init scripts unhappy at boot. I'll work on something for "/etc/init.d/hostname.sh" so that it doesn't fail on boot. Things just can't be easy, can they?</span></div>
<div><span style="background-color: transparent; "><br></span></div><div><span style="background-color: transparent; ">Tim Heckman</span></div>