diff options
| author | Beniamino Galvani <bgalvani@redhat.com> | 2016-10-08 10:27:15 +0200 |
|---|---|---|
| committer | Beniamino Galvani <bgalvani@redhat.com> | 2016-10-16 10:08:13 +0200 |
| commit | 51d7a18f2e09c0c9e36c5f2995a356e2737931f5 (patch) | |
| tree | d87a8e92b8817f1d5d2d4649892c78de18aa7d28 /libnm | |
| parent | 92a8cfac69d8ac00df94dc4da7a09d8f168d0c46 (diff) | |
libnm-core: introduce connection.autoconnect-retries property
While technically it's already possible to implement a fail-over
mechanism using multiple connections (for example, defining a higher
priority DHCP connection with short DHCP timeout and a lower priority
one with static address), in practice this doesn't work well as we try
to autoactivate each connection 4 times before switching to the next
one.
Introduce a connection.autoconnect-retries property that can be used
to change the number of retries. The special value 0 means infinite
and can be used to try the connection forever. A -1 value means the
global configured default, which is equal to 4 unless overridden.
https://bugzilla.gnome.org/show_bug.cgi?id=763524
Diffstat (limited to 'libnm')
| -rw-r--r-- | libnm/libnm.ver | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/libnm/libnm.ver b/libnm/libnm.ver index 46e91d9e9..b07b1d567 100644 --- a/libnm/libnm.ver +++ b/libnm/libnm.ver @@ -1088,6 +1088,7 @@ libnm_1_6_0 { global: nm_capability_get_type; nm_connection_get_setting_proxy; + nm_setting_connection_get_autoconnect_retries; nm_setting_proxy_get_type; nm_setting_proxy_new; nm_setting_proxy_get_method; |