On Mar 31, 2016 at 1:48 PM, Benjamin Lefoul <[log in to unmask]> wrote:
> On Mar 31, 2016 at 1:01 PM, Tom H <[log in to unmask]> wrote:
>>
>> Thanks for this. I meant to suggest in my last email that you ask on
>> the NM list but pressed "send" too quickly.
>>
>> So the problem's solved.
>>
>> But I'm tempted to add to the bug or file another one to request that
>> the "monitor-connection-files" of "man NetworkManager.conf" be
>> clarified because "NetworkManager will reload connection files any
>> time they changed" isn't going to be understood as "skip 'nmcli
>> connection reload'" but "run 'nmcli connection up <con-name>'" by
>> most:
>>
>> monitor-connection-files
>>     Whether the configured settings plugin(s) should set up file
>>     monitors and immediately pick up changes made to connection files
>>     while NetworkManager is running. This is disabled by default;
>>     NetworkManager will only read the connection files at startup, and
>>     when explicitly requested via the ReloadConnections D-Bus call. If
>>     this key is set to 'true', then NetworkManager will reload
>>     connection files any time they changed.


> (Sorry about not bottom-posting earlier, I hope this is better)

Thanks.


> I agree. I expect other people to be confused by this.
> A reasonable addition to this section of the man could be advising to
> use sudoedit to change connection in order to avoid unexpected
> behaviors, and reminding to use "nmcli con up $CONN" or better still,
> that new feature: "con reapply $CONN".

Some people might not have sudo installed so sudoedit isn't a
reasonable default recommendation.

But that section should mention that only the file's reloaded not the
connection, whether it mentions "nmcli connection up <con-name>"
specifically or not.