After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 583025 - change in /etc/sysconfig/network requires killing nm-system-settings
change in /etc/sysconfig/network requires killing nm-system-settings
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: general
0.7.x
Other All
: Normal normal
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2009-05-18 08:23 UTC by Marc
Modified: 2011-04-26 18:46 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Marc 2009-05-18 08:23:43 UTC 
Please describe the problem:
Changing the HOSTNAME line in /etc/sysconfig/network is ignored by nm-system-settings until it is manually killed. Worse: "/etc/init.d/NetworkManager restart" does NOT kill nm-system-settings.


Steps to reproduce:
1.  Change your HOSTNAME in /etc/sysconfig/network
2. unplug cable, replug cable, restart NM once, twice, do everything at the same time...
    => /etc/hosts never changes, and the 127.0.0.1 line in /etc/hosts stays out of date


(The workaround: killall nm-system-settings  => /etc/hosts is updated instantly)


Actual results:
HOSTNAME line in /etc/sysconfig/network is ignored

Expected results:
HOSTNAME line in /etc/sysconfig/network is considered

Does this happen every time?
yes

Other information:
See initial report here:
http://article.gmane.org/gmane.linux.network.networkmanager.devel/13240
Comment 1 Dan Williams 2011-04-26 18:46:06 UTC 
Shouldn't be a problem anymore with 0.8.x where nm-system-settings has been integrated into NM itself.