FS#32477 - [dhclient] Changes system hostname to the empty string
Attached to Project:
Arch Linux
Opened by Natanji (Natanji) - Monday, 05 November 2012, 18:29 GMT
Last edited by Laurent Carlier (lordheavy) - Sunday, 29 December 2013, 13:15 GMT
Opened by Natanji (Natanji) - Monday, 05 November 2012, 18:29 GMT
Last edited by Laurent Carlier (lordheavy) - Sunday, 29 December 2013, 13:15 GMT
|
Details
I noticed this in conjunction with wicd: the current
hostname setting logic of dhclient-script is severely
broken. In my case, I have not configured dhclient to change
the system's hostname based on DHCP in any way, but still I
often get an empty hostname after a connection attempt. This
is a well-known bug in other distributions, for instance in
debian - see
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609851
and
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635322
This is a very severe problem: many sockets of X applications are named by the current hostname, and this way rely on the hostname NEVER changing while the system is running. In my case I have to restart X whenever the hostname is changed, which is not acceptable. I am aware that our dhclient-script might be changed due to |
This task depends upon
Closed by Laurent Carlier (lordheavy)
Sunday, 29 December 2013, 13:15 GMT
Reason for closing: Fixed
Additional comments about closing: Solved
Sunday, 29 December 2013, 13:15 GMT
Reason for closing: Fixed
Additional comments about closing: Solved
Comment by Doug Newgard (Scimmia) -
Sunday, 29 September 2013, 22:43 GMT
Comment by Natanji (Natanji) -
Sunday, 29 September 2013, 23:19 GMT
Comment by Doug Newgard (Scimmia) -
Sunday, 29 September 2013, 23:30 GMT
Comment by Doug Newgard (Scimmia) -
Saturday, 28 December 2013, 16:22 GMT
Comment by Natanji (Natanji) -
Saturday, 28 December 2013, 16:40 GMT
Status? Arch is now using a heavily modified dhclient-script from
LFS.
I have not used dhclient for a while, but I just switched back to
test it out. I assume the dhclient-script is in the normal
dhclient package, not only in testing?
There isn't any in [testing] at the moment. The script change was
made back in March with 4.2.5-1
ping Natanji...
I haven't run into any problems anymore. So we can close this, I
think. :)