diff options
| author | Thomas Haller <thaller@redhat.com> | 2018-11-21 08:24:55 +0100 |
|---|---|---|
| committer | Thomas Haller <thaller@redhat.com> | 2018-12-09 14:47:31 +0100 |
| commit | c9354cb47771263b0762e0400de1b894fa480cd1 (patch) | |
| tree | c1d888b7296cc9bb48aefd036faac29a6eafe700 /src/nm-keep-alive.h | |
| parent | f95a5263667a03aaf67635d28532c242d3025bd9 (diff) | |
| download | NetworkManager-c9354cb47771263b0762e0400de1b894fa480cd1.tar.gz | |
keep-alive: drop unused nm_keep_alive_set_forced()
set-forced is currently unused, so drop it.
NMKeepAlive in principle determines the alive-status based on multiple
aspects, that in combination render the instance alive or dead. These
aspects cooperate in a particular way.
By default, a keep-alive instance should be alive. If there are conditions
enabled that further determine the alive-state, then these conditions
cooperate in a particular way. As it was, the force-flag would just
overrule them all.
But is that useful? The nm_keep_alive_set_forced() API also means that only
one user caller can have control over the flag. Independent callers cannot
cooperate on setting the flag, because there is no reference-counting or
registered handles.
At least today, it's unclear whether this flag really should overrule all
other conditions and how this flag would actually be used. Drop it for
now.
Diffstat (limited to 'src/nm-keep-alive.h')
| -rw-r--r-- | src/nm-keep-alive.h | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/src/nm-keep-alive.h b/src/nm-keep-alive.h index 72133224cd..160b2adb58 100644 --- a/src/nm-keep-alive.h +++ b/src/nm-keep-alive.h @@ -43,9 +43,6 @@ gboolean nm_keep_alive_is_alive (NMKeepAlive *self); void nm_keep_alive_arm (NMKeepAlive *self); void nm_keep_alive_disarm (NMKeepAlive *self); -void nm_keep_alive_set_forced (NMKeepAlive *self, - gboolean forced); - void nm_keep_alive_set_settings_connection_watch_visible (NMKeepAlive *self, NMSettingsConnection *connection); |