SCIENTIFIC-LINUX-USERS Archives

March 2016

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:
Reply To:
Date:
Thu, 31 Mar 2016 13:01:59 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (26 lines)
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.

ATOM RSS1 RSS2