diff options
| author | Thomas Haller <thaller@redhat.com> | 2017-02-16 20:10:19 +0100 |
|---|---|---|
| committer | Thomas Haller <thaller@redhat.com> | 2017-03-16 18:27:33 +0100 |
| commit | 90e7c8bf5bc91a48ba03be74e12702c07a1e06ee (patch) | |
| tree | 21554ae12b29520868654e8f34ff735675c59be6 /src/devices/nm-device.c | |
| parent | d43a54c9071caac2e09c2febcbcbfa1464321b2e (diff) | |
| download | NetworkManager-90e7c8bf5bc91a48ba03be74e12702c07a1e06ee.tar.gz | |
core/trivial: rename "nm-generated-assumed" flag to "volatile"
The concept of assumed-connection will change. Currently we mark
connections that are generated and assumed as "nm-generated-assumed".
That has several consequences, one of them being that such a settings
connection gets deleted when the device disconnects.
That is, such a settings connection lingers around as long as it's active,
but once it deactivates it gets automatically deleted. As such, it's
a more volatile concept of an in-memory connection.
The concept of such automatically cleaned up connections is useful beyond
generated-assumed. See the related bug rh#1401515.
Diffstat (limited to 'src/devices/nm-device.c')
| -rw-r--r-- | src/devices/nm-device.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/devices/nm-device.c b/src/devices/nm-device.c index 5252723cfe..a1fb1322f8 100644 --- a/src/devices/nm-device.c +++ b/src/devices/nm-device.c @@ -1606,7 +1606,7 @@ nm_device_uses_generated_assumed_connection (NMDevice *self) && nm_active_connection_get_assumed (NM_ACTIVE_CONNECTION (priv->act_request))) { connection = nm_act_request_get_settings_connection (priv->act_request); if ( connection - && nm_settings_connection_get_nm_generated_assumed (connection)) + && nm_settings_connection_get_volatile (connection)) return TRUE; } return FALSE; |