From 5c79b900b59a5ad162ecc836e424468207ff031e Mon Sep 17 00:00:00 2001
From: Michael Biebl if set, only secrets that
- are agent owned will be serialized.
diff --git a/docs/libnm/html/NMSettingIP6Config.html b/docs/libnm/html/NMSettingIP6Config.html
index 30ee1129..2cdd15c6 100644
--- a/docs/libnm/html/NMSettingIP6Config.html
+++ b/docs/libnm/html/NMSettingIP6Config.html
@@ -434,6 +434,7 @@ supported for IPv6)
#define NM_SETTING_IP6_CONFIG_METHOD_DISABLED "disabled"
IPv6 is disabled for the connection.
+Since: 1.20
return the number of ingress/egress priority entries, -1 if error
+return the number of ingress/egress priority entries.
out_from
on return the value of the priority map's 'from' item.
out_to
on return the value of priority map's 'to' item.
TRUE if the new priority mapping was successfully added to the
-list, FALSE if error
TRUE.
TRUE if the entry was successfully added to the list, or it
-overwrote the old value, FALSE if error
FALSE if str
+is not a valid mapping.
#define NM_SETTING_WIRELESS_MODE_MESH "mesh"
Indicates that the connection should create a mesh point.
+Since: 1.20
libnm Reference Manual |
|---|
- for libnm 1.19.90 + for libnm 1.20.0 The latest version of this documentation can be found on-line at https://developer.gnome.org/libnm/stable/. diff --git a/docs/libnm/html/libnm-nm-dbus-interface.html b/docs/libnm/html/libnm-nm-dbus-interface.html index 541a5a56..2e649502 100644 --- a/docs/libnm/html/libnm-nm-dbus-interface.html +++ b/docs/libnm/html/libnm-nm-dbus-interface.html @@ -1447,7 +1447,7 @@ GSM/UMTS, or LTE network access protocols
device supports acting as a mesh point
+device supports acting as a mesh point. Since: 1.20.
the device is a 802.11s mesh point.
+the device is a 802.11s mesh point. Since: 1.20.
indicates that the per-connection
setting is unspecified. In this case, it will fallback to the default
- value, which is NM_CONNECTION_MULTI_CONNECT_SINGLE
-.
NM_CONNECTION_MULTI_CONNECT_SINGLE.
this is almost the same as
+this is almost the same
+ as NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY, with one difference: when later deleting
+ the profile, the original profile will not be deleted. Instead a nmmeta
+ file is written to /run to indicate that the profile is gone.
+ Note that if such a nmmeta tombstone file exists and hides a file in persistant
+ storage, then when re-adding the profile with the same UUID, then the original
+ storage is taken over again.
this is like NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY
-,
+
this is like NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY,
but if the connection has a corresponding file on persistent storage, the file
will be deleted right away. If the profile is later again persisted to disk,
a new, unused filename will be chosen.
$cc $(pkg-config --libs --cflags libnm) -o hello-nm hello-nm.c$./hello-nm- NetworkManager version: 1.19.90 + NetworkManager version: 1.20.0$
-- cgit 1.3.0-6-gf8a5