At Thu, 05 Jan 2012 19:35:17 +0100, Michael Biebl wrote: > > On 05.01.2012 19:22, Jeroen Dekkers wrote: > > At Thu, 05 Jan 2012 14:42:33 +0100, > > Michael Biebl wrote: > >> Could you please attach your /etc/NetworkManager/nm-system-settings.conf > >> If you have the ifupdown plugin enabled (which is the default), then the > >> hostname configured in /etc/hostname should take precedence over the > >> DHCP provided hostname. > > > > My nm-system-settings.conf is: > > > > [main] > > no-auto-default=ETH0MACADDR, > > > > My NetworkManager.conf is: > > > > [main] > > plugins=ifupdown,keyfile > > > > [ifupdown] > > managed=false > > Ok, this is your problem then. You have both, the old and deprecated > nm-system-settings.conf file and the new NetworkManager.conf. > As the old file takes precedence, and your nm-system-settings.conf does > not contain plugins=ifupdown,keyfile, this might explain your problem. > > Please migrate any settings you have in nm-system-settings.conf to > NetworkManager.conf, and delete that file.
I can confirm this was the problem, after deleting the old file my hostname isn't changed anymore. > I'm not sure how you ended up having both config files. The Debian > package at least tries to migrate the settings in it postinst. It's possible that I downgraded network-manager in the past and that might explain having both configuration files. Kind regards, Jeroen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org