Re: NetworkManager-list Digest, Vol 49, Issue 2

[Dan Williams <dcbw redhat com>]

On Fri, 2008-10-03 at 17:42 -0400, Dustin Howett wrote:
> Done so, networkmanager reconnected, and my hostname got reset to
> localhost.localdomain.

Was your hostname 'localhost.localdomain' before the 'killall' ?  When
it starts up, the system settings service will grab the current hostname
and use that as a backup if no plugins support persistent hostnames.

Try setting the hostname to your preferred hostname, then do the
'killall', and see if the name changes.  Output of NM here would also be
helpful (from /var/log/messages or /var/log/daemon.log depending on your
distro).

Dan

> On Fri, Oct 3, 2008 at 5:36 PM, Dan Williams <dcbw redhat com> wrote:
> > On Fri, 2008-10-03 at 17:24 -0400, Dustin Howett wrote:
> >> On Fri, Oct 3, 2008 at 7:49 AM, Alexander Sack <asac jwsdot com> wrote:
> >> > On Thu, Oct 02, 2008 at 06:28:02PM -0400, Dustin Howett wrote:
> >> >> On Thu, Oct 2, 2008 at 3:20 PM, Dan Williams <dcbw redhat com> wrote:
> >> >> >
> >> >> > It's a matter of persistent storage... when you reboot you'd probably
> >> >> > like to have the hostname come back as what you set it before, and that
> >> >> > means you have to store the persistent hostname somewhere on the
> >> >> > filesystem...
> >> >> >
> >> >>
> >> >> This is completely true. I'd like to have my hostname remain what I
> >> >> set it; unfortunately, no matter what I set MY hostname to, NM insists
> >> >> on making me localhost.localdomain, no matter what.
> >> >> What might be better is some way to change it from nm or the related
> >> >> applet; without other system administration tools.
> >> >
> >> > The latest trunk builds shouldn't do that anymore. What build/package
> >> > are you using?
> >> >
> >>
> >> Latest trunk build straight from SVN as of not even 5 minutes ago,
> >> unfortunately.
> >
> > Did you reboot or 'killall -TERM nm-system-settings'?  One of those two
> > is necessary for the fix to take effect.
> >
> > Dan
> >
> >
> >
> 
> 
>