Re: [tlug] Um, so... systemd?

[Scott Robbins <scottro@example.com>]

On Fri, Jan 20, 2017 at 04:36:04PM +0900, Curt Sampson wrote:
> On 2017-01-19 05:55 -0500 (Thu), Scott Robbins wrote:
> 
> > On Thu, Jan 19, 2017 at 12:26:26PM +0900, Curt Sampson wrote:
> > > On 2017-01-19 11:45 +0900 (Thu), Edmund Edgar wrote:
> > > 
> > > > I fixed this by sprinkling "NM_CONTROLLED=no" liberally around the
> > > > interface definitions. To be on the safe side I guess I should disable
> > > > the network manager service entirely, and maybe get somebody in to do
> > > > an exorcism.
> > > 
> > > The incantation I use for that is `sudo yum remove NetworkManager`.
> > 
> 
> > I don't bother to remove [NetworkManager], because various updates
> > reinstall it.
> 
> Really? That sounds rather odd, since nothing normally run on a server
> should have a dependency on it. (I'd image that some of the graphical
> network management tools typically installed on desktop systems might,
> though.) Do you have more details on when you've seen this happen?

This is a server-cum-desktop and as I'm looking, I see I'm mistaken. Thak
you. What I do have though is NetworkManager-libnm.

> 
> > (And it is necessary, as Edmund mentioned to add the
> > NM_CONTROLLED=no to the ifcfg-whatever entries.)
> 
> Actually, that's necessary only if you actually run NetworkManager.
> The tests that look at it are of the form
> 
>     if is_nm_running ...
>         if ! is_false $NM_CONTROLLED; then

I would definitely take your word over mine. :)  I guess I've been doing it
for so long that it's become habit. 

Thank you, you corrected two bits of incorrect knowledge on my part.

-- 
Scott Robbins
PGP keyID EB3467D6
( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 )
gpg --keyserver pgp.mit.edu --recv-keys EB3467D6