On Sat, Mar 14, 2015 at 12:39:18PM +0000, Mike Gabriel wrote: > > I am seeing several thin-client-server installations and workstation > installations that have eth0 not managed by network-manager and thus the > hostname update via DHCP does not happen. > > Is that intended (using ifupdown for management of eth0)? To me it seems to > be a bug (and a regression compared to squeeze/wheezy). The hostname is updated via /etc/dhcp/dhclient-exit-hooks.d/hostname (like it is done in wheezy). But for some reason it now takes about 15 minutes to take effect if a new or just renamed system is connected. Running 'systemctl restart networking.service' updates the hostname immediately. (As observed since a long time in a d-e virtualbox environment.) I just had the chance to test this w/ real hardware, same behaviour. Wolfgang
Attachment:
signature.asc
Description: Digital signature