More doc improvements

This commit is contained in:
Pavel Cahyna 2018-10-04 15:51:05 +02:00 committed by pcahyna
parent ddada6e4c9
commit 979145cbae

View file

@ -142,7 +142,7 @@ Note that if the `state` option is unset, the connection profiles runtime sta
### `persistent_state`
The `persistent_state` option identifies if a connection profile is in a persistent state. The `persistent_state` option can be set to the following values:
The `persistent_state` option identifies if a connection profile is persistent (saved on disk). The `persistent_state` option can be set to the following values:
#### `persistent_state: present` (default)
@ -152,6 +152,10 @@ incomplete (no `type` option), the behavior is undefined. Also, the `present` va
does not directly result in a change in the network configuration. If the `state` option
is not set to `up`, the profile is only created or modified, not activated.
For NetworkManager, the new connection profile is created with the `autoconnect`
option enabled by default. Therefore, NetworkManager can activate the new
profile on a currently disconnected device. ([rh#1401515](https://bugzilla.redhat.com/show_bug.cgi?id=1401515)).
#### `persistent_state: absent`
The `absent` value ensures that the profile is not present on the
@ -228,10 +232,6 @@ role.
### `autoconnect`
For NetworkManager, the new connection profile is created when the `autoconnect`
option is enabled by default. Therefore, NetworkManager can activate the new
profile on a currently disconnected device. ([rh#1401515](https://bugzilla.redhat.com/show_bug.cgi?id=1401515)).
By default, profiles are created with autoconnect enabled.
- For `NetworkManager`, this corresponds to the `connection.autoconnect` property.