Hi there,
I experience a problem with hostname manipulation of NetworkManager
and the X session. DHCP server sends a hostname within the dhcp
offer, which is different the current one. There is no persistent
hostname definition within the 'nm-system-settings.conf' as this is a
default installation. NetworkManager just changes the hostname and as
new hostname is not authenticated (xhost cookie MIT-MAGIC-COOKIE-1 for
new hostname does not exist) no new application can be started
afterwards.
To avoid this behavior, I can define a persistent hostname equal the
content of /etc/HOSTNAME (this is a slackware system) as the
following:
--- /etc/NetworkManager/nm-system-settings.conf~
+++ /etc/NetworkManager/nm-system-settings.conf
@@ -1,2 +1,5 @@
[main]
plugins=keyfile
+
+[keyfile]
+hostname=myhostname
As persistent hostname has highest precedence, problem looks solved;
but this should be repeated for each installation.
What I'm asking is, is there any config option or some way to not let
NetworkManager change the hostname?
As a note, current precedence order for hostname (taken from
NetworkManagerPolicy.c):
* 1) a configured hostname (from system-settings)
* 2) automatic hostname from the default device's config (DHCP, VPN,
etc)
* 3) the original hostname when NM started
* 4) reverse-DNS of the best device's IPv4 address
Thanks,
Firat
_______________________________________________
networkmanager-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/networkmanager-list
