SCIENTIFIC-LINUX-USERS Archives

April 2017

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"~Stack~" <[log in to unmask]>
Reply To:
~Stack~
Date:
Sun, 9 Apr 2017 14:04:56 -0500
Content-Type:
multipart/signed
Parts/Attachments:
text/plain (2135 bytes) , signature.asc (834 bytes)
On 04/08/2017 04:36 PM, ~Stack~ wrote:
<snip>

> They mention taking down a network with:
> $ nmcli dev disconnect interface-name
>
> but bringing it up with:
> $ nmcli con up interface-name
> That is so infuriating to me. Why use different sub-commands? Especially
> when there exist subcommands in the same context? Why not do this?
> $ nmcli dev disconnect interface-name
> $ nmcli dev connect interface-name
> 
> Or even this?
> $ nmcli con down interface-name
> $ nmcli con up interface-name
> 
> As far as I can tell, they are both doing the same thing. In fact the
> only difference I can tell comes from the nmcli help documentation where
> it says the difference is in the auto-activating:
> 
> $ nmcli d disconnect --help
> <snip>
> The command disconnects the device and prevents it from auto-activating
> further connections without user/manual intervention.
> 
> $ nmcli connection down --help
> <snip>
> Deactivate a connection from a device (without preventing the device
> from further auto-activation). <snip>
<snip>

Sorry for replying to my own question, but thought I would post some
relevant information.

I pinged a friend that has quite a few more RH certs than I do and asked
him. He didn't have an definitive answer. However he commented that he
makes the distinction precisely because of what I found. He said that
doing a "con down" means that any automated check or script or anything
may trigger that connection to come back up which he explicitly doesn't
want happening while he is editing files, testing configurations, ect.
Thus, a "dev disconnect" ensures it stays down till he wants it back up.
However, he also mentioned that he brings the interface up with "dev
connect" and as far as he knows he hasn't had issues. He recommended
just using "dev disconnect" and "dev connect".

It isn't a perfect answer for me as I still want to know why RH and
others recommend the method that they do, but it is at least a more
sensible answer than what I have found on my own searching the internet. :-)

I actually do have the ability to pester RH directly. I may do so and
see what they say. If I do ask, I will share if I find out. ;-)

Thanks!
~Stack~



ATOM RSS1 RSS2