Changing host name

[Paul W. Frields]

On Wed, Apr 07, 2010 at 06:16:39PM -0700, Rick Stevens wrote:
> On 04/07/2010 06:03 PM, Paul W. Frields wrote:
> > On Wed, Apr 07, 2010 at 01:34:35PM -0700, Rick Stevens wrote:
> >> On 04/07/2010 10:51 AM, Tom H wrote:
> >>>>>>> I've never found a need to reboot on changing hostnames.  The most
> >>>>>>> drastic action I've taken was to "service network restart".
> >>>
> >>>>>> One wold assumme if yo are using 'service network start' you are not
> >>>>>> using NM so your comments about the changing hostname may not apply to
> >>>>>> the OP's system.
> >>>
> >>>>> Unless I'm out of my mind...that assumption would not be true.....
> >>>>> Even if you use NM you can still use "service network restart".  When
> >>>>> one uses NM the directories /etc/sysconfig/networking/profiles/default
> >>>>> and /etc/sysconfig/networking/devices are empty. This is the case on my
> >>>>> system.
> >>
> >> I would highly recommend you DON'T use "service network restart" if
> >> you're using NM.  The two are not compatible in many areas.
> >>
> >>>> I have no opinion on the soundness of this, but "service NetworkManager
> >>>> restart" is what I use myself.
> >>
> >> I believe that's what's required if you do some manual reconfig of the
> >> network behind NM's back.
> >>
> >>> There is a "NM_CONTROLLED" variable that can be set in the ifcfg-*
> >>> scripts to use one or the other (although I do not see where my F13
> >>> init.d scripts check for its value.)
> >>
> >> I'm not sure they do.  I believe the idea is that NM would ONLY futz
> >> with interfaces marked thus and leave the others alone.
> >>
> >> With both classic and NM enabled, the normal startup sequence would
> >> "service network start" at sequence 10, then "service NetworkManager
> >> start" at sequence 23  The way I read it, classic could play with all
> >> the NICs and NM would only touch the ones marked "NM_CONTROLLED",
> >> undoing what classic did to them.
> >
> > Just to be clear, NM_CONTROLLED is not a marker, it's a variable.  You
> > would set NM_CONTROLLED=no for an interface where you didn't want NM
> > to monitor or change its state.
> 
> Yes, it is a variable.  If the content of it is anything other than
> "yes" or if the variable isn't defined, NM is supposed to ignore the
> interface.
> 
> I won't swear to that.  There's virtually no NM documentation.

Not really true -- you might want to check here for some helpful
stuff:

http://live.gnome.org/NetworkManager
	(lots of docs)
http://live.gnome.org/NetworkManager/SystemSettings
	(specific stuff on system settings integration with distros)

-- 
Paul W. Frields                                http://paul.frields.org/
  gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233  5906 ACDB C937 BD11 3717
  http://redhat.com/   -  -  -  -   http://pfrields.fedorapeople.org/
          Where open source multiplies: http://opensource.com