Commit 07bd9a1b authored by Jiří Klimeš's avatar Jiří Klimeš Committed by Dan Winship

man: ifcfg-rh manual page text update

parent c7341c98
......@@ -51,7 +51,7 @@
for static IPv4 routes and <filename>route6-*</filename> for static IPv6 routes.
The plugin currently supports reading and writing Ethernet, Wi-Fi, InfiniBand,
VLAN, Bond, Bridge, and Team connections. Unsupported connection types (such as
(WWAN, PPPoE, VPN, or ADSL) are handled by <emphasis>keyfile</emphasis> plugin
WWAN, PPPoE, VPN, or ADSL are handled by <emphasis>keyfile</emphasis> plugin
(<citerefentry><refentrytitle>nm-settings-keyfile</refentrytitle><manvolnum>5</manvolnum></citerefentry>).
The main reason for using <emphasis>ifcfg-rh</emphasis> plugin is the compatibility
with legacy configurations for <emphasis>ifup</emphasis> and <emphasis>ifdown</emphasis>
......@@ -273,8 +273,8 @@ DEVICETYPE=TeamPort
Each secret property in a NetworkManager setting has an associated
<emphasis>flags</emphasis> property that describes how to handle that secret.
In the <emphasis>fcfg-rh</emphasis> plugin variables for secret flags have a
<emphasis>-FLAGS</emphasis> suffix. The variables contain one or more of the
folowing values (space separated). Missing (or empty) -FLAGS variable means
<emphasis>_FLAGS</emphasis> suffix. The variables contain one or more of the
folowing values (space separated). Missing (or empty) *_FLAGS variable means
that the password is owned by NetworkManager.
</para>
<itemizedlist>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment