|
From: | Thomas Danckaert |
Subject: | Re: networkmanager hostname woes |
Date: | Sat, 16 Sep 2017 08:57:24 +0200 (CEST) |
From: ng0 <address@hidden> Subject: Re: networkmanager hostname woes Date: Fri, 15 Sep 2017 12:14:49 +0000
Arun Isaac transcribed 0.8K bytes:Thomas Danckaert writes:> AFAIU, the cause is that networkmanager changes my hostname (after> DHCP?), in my case to “new-host2” or something similar, and this> seems to break the X session. When I manually restore the hostname > with “sudo hostname <original-hostname>”, the problem is solved. Is> there anyway to disable this behaviour for networkmanager?I have the exact same problem too. If somebody has a solution, I'd liketo hear about it.I don't understand your problem.
The problem is that changing the hostname after starting an X session, breaks that session.
This is public documented behavior of NM.
Can you point me to the networkmanager documentation? Could help to find a proper way to configure this (adding some configuration options to our networkmanager service perhaps). I couldn't immediately find anything helpful.
Assuming that we build networkmanager with dhclient option/configure:
seems like we do: the networkmanager package in in gnu/packages/gnome.scm has an option (string-append "--with-dhclient=" dhclient)))
add to /etc/dhcp/dhclient.conf: send host-name "yourhostname";
I think some people prefer not to send their own hostname to any router they connect to (assuming that's what “send host-name” does :-) ). Do you think creating /etc/hostname instead is not a good solution?
Thanks! Thomas
[Prev in Thread] | Current Thread | [Next in Thread] |