diff options
| author | Thomas Haller <thaller@redhat.com> | 2018-10-26 09:05:41 +0200 |
|---|---|---|
| committer | Thomas Haller <thaller@redhat.com> | 2018-10-26 09:06:45 +0200 |
| commit | 085b769729e9c623cc60bb0f88df36d1843cd22b (patch) | |
| tree | 16db52e2ec93af5ad4839a08f86cc22718042b8d | |
| parent | f120bbc7a81982690a3f656cfa8156b1aaee40f0 (diff) | |
man: clarify udev property "NM_UNMANAGED" in `man NetworkManager`
| -rw-r--r-- | man/NetworkManager.xml | 17 |
1 files changed, 7 insertions, 10 deletions
diff --git a/man/NetworkManager.xml b/man/NetworkManager.xml index f78a44f4f8..22d07b8f91 100644 --- a/man/NetworkManager.xml +++ b/man/NetworkManager.xml @@ -437,16 +437,13 @@ <varlistentry> <term><varname>NM_UNMANAGED</varname></term> <listitem><para> - No default connection will be created and automatic activation - will not be attempted when this property of a device is set to a - true value ("1" or "true"). You will still be able to attach a - connection to the device manually or observe externally added - configuration such as addresses or routes. - </para><para> - Create an udev rule that sets this property to prevent NetworkManager - from interfering with virtual Ethernet device interfaces that are - managed by virtualization tools. - </para></listitem> + If set to <literal>"1"</literal> or <literal>"true"</literal>, the device is + configured as unmanaged by NetworkManager. Note that the user still can + explicitly overrule this configuration via means like + <command>nmcli device set "$DEVICE" managed yes</command> or + <literal>"device*.managed=1"</literal> in NetworkManager.conf. + </para> + </listitem> </varlistentry> </variablelist> </refsect1> |