________________________________________
From: [log in to unmask] <[log in to unmask]> on behalf of Tom H <[log in to unmask]>
Sent: 31 March 2016 13:01
To: SL Users
Subject: Re: How does NetworkManager monitor the connection files?

On Thu, Mar 31, 2016 at 10:46 AM, Benjamin Lefoul
<[log in to unmask]> wrote:
>
> Done with bug 764402: https://bugzilla.gnome.org/show_bug.cgi?id=764402

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)

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".

Benjamin Lefoul
nWISE AB