Re: Stop nm-system-settings when NM is stopped

[Dan Williams <dcbw redhat com>]

On Fri, 2009-05-15 at 12:16 +0100, Marc Herbert wrote:
> Dan Williams a écrit :
> > On Tue, 2009-04-21 at 11:02 +0100, Marc Herbert wrote:
> >> Michael Biebl a écrit :
> >>
> >>> since NM 0.7 has hit the Debian archive, I got several bug reports, where users
> >>> changed the configuration in /etc/network/interfaces, restarted NetworkManager
> >>> (via /etc/init.d/network-manager restart), and wondered, why their changes were
> >>> not picked up.
> >> Same problem here when changing HOSTNAME in /etc/sysconfig/network on Fedora 10: ignored until next reboot. 
> > 
> > It should be immediate.  If it's not, that's a bug in the ifcfg-rh
> > plugin or in NM.
> 
> Then it is a bug, confirmed in 0.7.1 release 1.fc10
> 
> - Change your HOSTNAME in /etc/sysconfig/network
> 
> - 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
> 
> - run: killall nm-system-settings
>     => /etc/hosts is updated instantly
> 
> Except nm-system-settings is never supposed to be restarted!
> 
> Is it worth filing it despite nm-system-settings bound to disappear?

Yeah, it's worth filing.

Dan