[Bug 537978] Re: Lucid dhclient can't set hostname
The upstart task sets the system hostname from /etc/hostname (falling back to localhost if that file is not readable or is empty and no hostname has yet been set). The idea here would be honor new_host_name for the same use cases (if the /etc/hostname file is non-empty). That would support both the first case (honor DHCP new_host_name if no hostname=localhost) and the case the debian bug tries to cover (honor further DHCP new_host_name if hostname was previously set by DHCP) Something like: if [ -n $new_host_name ]; then if [ ! -s /etc/hostname ]; then hostname $new_host_name fi fi ** Changed in: dhcp3 (Ubuntu Lucid) Status: Triaged = In Progress ** Changed in: dhcp3 (Ubuntu Lucid) Assignee: (unassigned) = Thierry Carrez (ttx) -- Lucid dhclient can't set hostname https://bugs.launchpad.net/bugs/537978 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 537978] Re: Lucid dhclient can't set hostname
This bug was fixed in the package dhcp3 - 3.1.3-2ubuntu3 --- dhcp3 (3.1.3-2ubuntu3) lucid; urgency=low * debian/dhclient-script.linux: Fix regression in host_name option handling, so that it's always honored when /etc/hostname is not set, fixes LP: #537978, #482313, #90388, #476491 -- Thierry Carrez thierry.car...@ubuntu.com Thu, 01 Apr 2010 16:52:36 +0200 ** Changed in: dhcp3 (Ubuntu Lucid) Status: In Progress = Fix Released -- Lucid dhclient can't set hostname https://bugs.launchpad.net/bugs/537978 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 537978] Re: Lucid dhclient can't set hostname
Thierry, hostname is set by upstart so the point is moot I think. Regards chuck -- Lucid dhclient can't set hostname https://bugs.launchpad.net/bugs/537978 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 537978] Re: Lucid dhclient can't set hostname
Regression was introduced by the fix to: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508804 It could be fixed by fixing the obviously wrong patch, and support two cases: * Set hostname if new_host_name provided and hostname is not set * Set hostname if new_host_name provided and old_host_name matches the current hostname Something like local current_hostname=$(hostname) if [ -z $current_hostname -o $current_hostname = (none) -o $current_hostname = localhost -o $current_hostname = $old_host_name ]; then if [ -n $new_host_name ]; then hostname $new_host_name fi fi However I am not so sure we should support the use case of the debian bug since option host-name should only be honored by dhclient-script(8) if the hostname for the client machine is not set... Bug 482313 would be fixed in the same run (by adding localhost to the set of hostnames considered unset). ** Bug watch added: Debian Bug tracker #508804 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508804 ** Changed in: dhcp3 (Ubuntu) Status: Confirmed = Triaged ** Also affects: dhcp3 (Ubuntu Lucid) Importance: Medium Status: Triaged -- Lucid dhclient can't set hostname https://bugs.launchpad.net/bugs/537978 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 537978] Re: Lucid dhclient can't set hostname
The live-CD has an /etc/hostname set to ubuntu, so what do you want me to check? Apart from that, the /sbin/dhclient-script file is the same as above, so the logic to change the hostname does not work and is not conforming to the dhclient-documentation. -- Lucid dhclient can't set hostname https://bugs.launchpad.net/bugs/537978 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 537978] Re: Lucid dhclient can't set hostname
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Lucid Lynx. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help. ** Changed in: dhcp3 (Ubuntu) Importance: Undecided = Medium ** Changed in: dhcp3 (Ubuntu) Status: New = Confirmed -- Lucid dhclient can't set hostname https://bugs.launchpad.net/bugs/537978 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
