From d0425f68f7ee83a1dc5a6ad3688627c1b472a58b Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Mon, 30 Sep 2019 13:49:20 +0200 Subject: New upstream version 1.20.4 --- docs/libnm/html/libnm-nm-dbus-interface.html | 336 +++++++++++++-------------- 1 file changed, 168 insertions(+), 168 deletions(-) (limited to 'docs/libnm/html/libnm-nm-dbus-interface.html') diff --git a/docs/libnm/html/libnm-nm-dbus-interface.html b/docs/libnm/html/libnm-nm-dbus-interface.html index 65f3dfda..2e649502 100644 --- a/docs/libnm/html/libnm-nm-dbus-interface.html +++ b/docs/libnm/html/libnm-nm-dbus-interface.html @@ -8,7 +8,7 @@ - + @@ -920,11 +920,11 @@ extensions.

NM_STATE_UNKNOWN

Networking state is unknown. This indicates a daemon error -that makes it unable to reasonably assess the state. In such event the -applications are expected to assume Internet connectivity might be present -and not disable controls that require network access. -The graphical shells may hide the network accessibility indicator altogether -since no meaningful status indication can be provided.

+ that makes it unable to reasonably assess the state. In such event the + applications are expected to assume Internet connectivity might be present + and not disable controls that require network access. + The graphical shells may hide the network accessibility indicator altogether + since no meaningful status indication can be provided.

@@ -932,7 +932,7 @@ since no meaningful status indication can be provided.

NM_STATE_ASLEEP

Networking is not enabled, the system is being suspended or -resumed from suspend.

+ resumed from suspend.

@@ -940,8 +940,8 @@ resumed from suspend.

NM_STATE_DISCONNECTED

There is no active network connection. -The graphical shell should indicate no network connectivity and the -applications should not attempt to access the network.

+ The graphical shell should indicate no network connectivity and the + applications should not attempt to access the network.

@@ -949,7 +949,7 @@ applications should not attempt to access the network.

NM_STATE_DISCONNECTING

Network connections are being cleaned up. -The applications should tear down their network sessions.

+ The applications should tear down their network sessions.

@@ -957,8 +957,8 @@ The applications should tear down their network sessions.

NM_STATE_CONNECTING

A network connection is being started -The graphical shell should indicate the network is being connected while -the applications should still make no attempts to connect the network.

+ The graphical shell should indicate the network is being connected while + the applications should still make no attempts to connect the network.

@@ -966,8 +966,8 @@ the applications should still make no attempts to connect the network.

NM_STATE_CONNECTED_LOCAL

There is only local IPv4 and/or IPv6 connectivity, -but no default route to access the Internet. The graphical shell should -indicate no network connectivity.

+ but no default route to access the Internet. The graphical shell should + indicate no network connectivity.

@@ -975,9 +975,9 @@ indicate no network connectivity.

NM_STATE_CONNECTED_SITE

There is only site-wide IPv4 and/or IPv6 connectivity. -This means a default route is available, but the Internet connectivity check -(see "Connectivity" property) did not succeed. The graphical shell should -indicate limited network connectivity.

+ This means a default route is available, but the Internet connectivity check + (see "Connectivity" property) did not succeed. The graphical shell should + indicate limited network connectivity.

@@ -985,8 +985,8 @@ indicate limited network connectivity.

NM_STATE_CONNECTED_GLOBAL

There is global IPv4 and/or IPv6 Internet connectivity -This means the Internet connectivity check succeeded, the graphical shell should -indicate full network connectivity.

+ This means the Internet connectivity check succeeded, the graphical shell should + indicate full network connectivity.

@@ -1010,9 +1010,9 @@ indicate full network connectivity.

NM_CONNECTIVITY_UNKNOWN

Network connectivity is unknown. This means the -connectivity checks are disabled (e.g. on server installations) or has -not run yet. The graphical shell should assume the Internet connection -might be available and not present a captive portal window.

+ connectivity checks are disabled (e.g. on server installations) or has + not run yet. The graphical shell should assume the Internet connection + might be available and not present a captive portal window.

@@ -1020,9 +1020,9 @@ might be available and not present a captive portal window.

NM_CONNECTIVITY_NONE

The host is not connected to any network. There's -no active connection that contains a default route to the internet and -thus it makes no sense to even attempt a connectivity check. The graphical -shell should use this state to indicate the network connection is unavailable.

+ no active connection that contains a default route to the internet and + thus it makes no sense to even attempt a connectivity check. The graphical + shell should use this state to indicate the network connection is unavailable.

@@ -1030,11 +1030,11 @@ shell should use this state to indicate the network connection is unavailable.

NM_CONNECTIVITY_PORTAL

The Internet connection is hijacked by a captive -portal gateway. The graphical shell may open a sandboxed web browser window -(because the captive portals typically attempt a man-in-the-middle attacks -against the https connections) for the purpose of authenticating to a gateway -and retrigger the connectivity check with CheckConnectivity() when the -browser window is dismissed.

+ portal gateway. The graphical shell may open a sandboxed web browser window + (because the captive portals typically attempt a man-in-the-middle attacks + against the https connections) for the purpose of authenticating to a gateway + and retrigger the connectivity check with CheckConnectivity() when the + browser window is dismissed.

@@ -1042,8 +1042,8 @@ browser window is dismissed.

NM_CONNECTIVITY_LIMITED

The host is connected to a network, does not appear -to be able to reach the full Internet, but a captive portal has not been -detected.

+ to be able to reach the full Internet, but a captive portal has not been + detected.

@@ -1051,7 +1051,7 @@ detected.

NM_CONNECTIVITY_FULL

The host is connected to a network, and -appears to be able to reach the full Internet.

+ appears to be able to reach the full Internet.

@@ -1643,8 +1643,8 @@ supported

NM_802_11_MODE_ADHOC

for both devices and access point objects, indicates -the object is part of an Ad-Hoc 802.11 network without a central -coordinating access point.

+ the object is part of an Ad-Hoc 802.11 network without a central + coordinating access point.

@@ -1652,9 +1652,9 @@ coordinating access point.

NM_802_11_MODE_INFRA

the device or access point is in infrastructure mode. -For devices, this indicates the device is an 802.11 client/station. For -access point objects, this indicates the object is an access point that -provides connectivity to clients.

+ For devices, this indicates the device is an 802.11 client/station. For + access point objects, this indicates the object is an access point that + provides connectivity to clients.

@@ -1662,7 +1662,7 @@ provides connectivity to clients.

NM_802_11_MODE_AP

the device is an access point/hotspot. Not valid for -access point objects; used only for hotspot mode on the local machine.

+ access point objects; used only for hotspot mode on the local machine.

@@ -1842,7 +1842,7 @@ GPRS, EDGE, UMTS, HSDPA, HSUPA, or HSPA+ packet switched data capability

NM_DEVICE_STATE_UNMANAGED

the device is recognized, but not managed by -NetworkManager

+ NetworkManager

@@ -1850,9 +1850,9 @@ NetworkManager

NM_DEVICE_STATE_UNAVAILABLE

the device is managed by NetworkManager, but -is not available for use. Reasons may include the wireless switched off, -missing firmware, no ethernet carrier, missing supplicant or modem manager, -etc.

+ is not available for use. Reasons may include the wireless switched off, + missing firmware, no ethernet carrier, missing supplicant or modem manager, + etc.

@@ -1860,7 +1860,7 @@ etc.

NM_DEVICE_STATE_DISCONNECTED

the device can be activated, but is currently -idle and not connected to a network.

+ idle and not connected to a network.

@@ -1868,9 +1868,9 @@ idle and not connected to a network.

NM_DEVICE_STATE_PREPARE

the device is preparing the connection to the -network. This may include operations like changing the MAC address, -setting physical link properties, and anything else required to connect -to the requested network.

+ network. This may include operations like changing the MAC address, + setting physical link properties, and anything else required to connect + to the requested network.

@@ -1878,8 +1878,8 @@ to the requested network.

NM_DEVICE_STATE_CONFIG

the device is connecting to the requested network. -This may include operations like associating with the Wi-Fi AP, dialing -the modem, connecting to the remote Bluetooth device, etc.

+ This may include operations like associating with the Wi-Fi AP, dialing + the modem, connecting to the remote Bluetooth device, etc.

@@ -1887,8 +1887,8 @@ the modem, connecting to the remote Bluetooth device, etc.

NM_DEVICE_STATE_NEED_AUTH

the device requires more information to continue -connecting to the requested network. This includes secrets like WiFi -passphrases, login passwords, PIN codes, etc.

+ connecting to the requested network. This includes secrets like WiFi + passphrases, login passwords, PIN codes, etc.

@@ -1896,7 +1896,7 @@ passphrases, login passwords, PIN codes, etc.

NM_DEVICE_STATE_IP_CONFIG

the device is requesting IPv4 and/or IPv6 -addresses and routing information from the network.

+ addresses and routing information from the network.

@@ -1904,9 +1904,9 @@ addresses and routing information from the network.

NM_DEVICE_STATE_IP_CHECK

the device is checking whether further action is -required for the requested network connection. This may include checking -whether only local network access is available, whether a captive portal -is blocking access to the Internet, etc.

+ required for the requested network connection. This may include checking + whether only local network access is available, whether a captive portal + is blocking access to the Internet, etc.

@@ -1914,8 +1914,8 @@ is blocking access to the Internet, etc.

NM_DEVICE_STATE_SECONDARIES

the device is waiting for a secondary -connection (like a VPN) which must activated before the device can be -activated

+ connection (like a VPN) which must activated before the device can be + activated

@@ -1923,7 +1923,7 @@ activated

NM_DEVICE_STATE_ACTIVATED

the device has a network connection, either local -or global.

+ or global.

@@ -1931,8 +1931,8 @@ or global.

NM_DEVICE_STATE_DEACTIVATING

a disconnection from the current network -connection was requested, and the device is cleaning up resources used for -that connection. The network connection may still be valid.

+ connection was requested, and the device is cleaning up resources used for + that connection. The network connection may still be valid.

@@ -1940,7 +1940,7 @@ that connection. The network connection may still be valid.

NM_DEVICE_STATE_FAILED

the device failed to connect to the requested -network and is cleaning up the connection request

+ network and is cleaning up the connection request

@@ -2509,8 +2509,8 @@ network and is cleaning up the connection request

NM_CONNECTION_MULTI_CONNECT_DEFAULT

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.

+ setting is unspecified. In this case, it will fallback to the default + value, which is NM_CONNECTION_MULTI_CONNECT_SINGLE.

@@ -2518,8 +2518,8 @@ value, which is

NM_CONNECTION_MULTI_CONNECT_SINGLE

the connection profile can only -be active once at each moment. Activating a profile that is already active, -will first deactivate it.

+ be active once at each moment. Activating a profile that is already active, + will first deactivate it.

@@ -2527,9 +2527,9 @@ will first deactivate it.

NM_CONNECTION_MULTI_CONNECT_MANUAL_MULTIPLE

the profile can -be manually activated multiple times on different devices. However, -regarding autoconnect, the profile will autoconnect only if it is -currently not connected otherwise.

+ be manually activated multiple times on different devices. However, + regarding autoconnect, the profile will autoconnect only if it is + currently not connected otherwise.

@@ -2537,7 +2537,7 @@ currently not connected otherwise.

NM_CONNECTION_MULTI_CONNECT_MULTIPLE

the profile can autoactivate -and be manually activated multiple times together.

+ and be manually activated multiple times together.

@@ -2586,7 +2586,7 @@ network.

NM_ACTIVE_CONNECTION_STATE_DEACTIVATING

the network connection is being -torn down and cleaned up

+ torn down and cleaned up

@@ -2594,7 +2594,7 @@ torn down and cleaned up

NM_ACTIVE_CONNECTION_STATE_DEACTIVATED

the network connection is disconnected -and will be removed

+ and will be removed

@@ -2619,7 +2619,7 @@ and will be removed

NM_ACTIVE_CONNECTION_STATE_REASON_UNKNOWN

The reason for the active connection -state change is unknown.

+ state change is unknown.

@@ -2627,7 +2627,7 @@ state change is unknown.

NM_ACTIVE_CONNECTION_STATE_REASON_NONE

No reason was given for the active -connection state change.

+ connection state change.

@@ -2635,7 +2635,7 @@ connection state change.

NM_ACTIVE_CONNECTION_STATE_REASON_USER_DISCONNECTED

The active connection changed -state because the user disconnected it.

+ state because the user disconnected it.

@@ -2643,7 +2643,7 @@ state because the user disconnected it.

NM_ACTIVE_CONNECTION_STATE_REASON_DEVICE_DISCONNECTED

The active connection -changed state because the device it was using was disconnected.

+ changed state because the device it was using was disconnected.

@@ -2651,7 +2651,7 @@ changed state because the device it was using was disconnected.

NM_ACTIVE_CONNECTION_STATE_REASON_SERVICE_STOPPED

The service providing the -VPN connection was stopped.

+ VPN connection was stopped.

@@ -2659,7 +2659,7 @@ VPN connection was stopped.

NM_ACTIVE_CONNECTION_STATE_REASON_IP_CONFIG_INVALID

The IP config of the active -connection was invalid.

+ connection was invalid.

@@ -2667,7 +2667,7 @@ connection was invalid.

NM_ACTIVE_CONNECTION_STATE_REASON_CONNECT_TIMEOUT

The connection attempt to -the VPN service timed out.

+ the VPN service timed out.

@@ -2675,7 +2675,7 @@ the VPN service timed out.

NM_ACTIVE_CONNECTION_STATE_REASON_SERVICE_START_TIMEOUT

A timeout occurred -while starting the service providing the VPN connection.

+ while starting the service providing the VPN connection.

@@ -2683,7 +2683,7 @@ while starting the service providing the VPN connection.

NM_ACTIVE_CONNECTION_STATE_REASON_SERVICE_START_FAILED

Starting the service -providing the VPN connection failed.

+ providing the VPN connection failed.

@@ -2691,7 +2691,7 @@ providing the VPN connection failed.

NM_ACTIVE_CONNECTION_STATE_REASON_NO_SECRETS

Necessary secrets for the -connection were not provided.

+ connection were not provided.

@@ -2699,7 +2699,7 @@ connection were not provided.

NM_ACTIVE_CONNECTION_STATE_REASON_LOGIN_FAILED

Authentication to the -server failed.

+ server failed.

@@ -2707,7 +2707,7 @@ server failed.

NM_ACTIVE_CONNECTION_STATE_REASON_CONNECTION_REMOVED

The connection was -deleted from settings.

+ deleted from settings.

@@ -2715,7 +2715,7 @@ deleted from settings.

NM_ACTIVE_CONNECTION_STATE_REASON_DEPENDENCY_FAILED

Master connection of this -connection failed to activate.

+ connection failed to activate.

@@ -2723,7 +2723,7 @@ connection failed to activate.

NM_ACTIVE_CONNECTION_STATE_REASON_DEVICE_REALIZE_FAILED

Could not create the -software device link.

+ software device link.

@@ -2731,7 +2731,7 @@ software device link.

NM_ACTIVE_CONNECTION_STATE_REASON_DEVICE_REMOVED

The device this connection -depended on disappeared.

+ depended on disappeared.

@@ -2757,8 +2757,8 @@ depended on disappeared.

NM_SECRET_AGENT_GET_SECRETS_FLAG_NONE

no special behavior; by default no -user interaction is allowed and requests for secrets are fulfilled from -persistent storage, or if no secrets are available an error is returned.

+ user interaction is allowed and requests for secrets are fulfilled from + persistent storage, or if no secrets are available an error is returned.

@@ -2766,8 +2766,8 @@ persistent storage, or if no secrets are available an error is returned.

NM_SECRET_AGENT_GET_SECRETS_FLAG_ALLOW_INTERACTION

allows the request to -interact with the user, possibly prompting via UI for secrets if any are -required, or if none are found in persistent storage.

+ interact with the user, possibly prompting via UI for secrets if any are + required, or if none are found in persistent storage.

@@ -2775,9 +2775,9 @@ required, or if none are found in persistent storage.

NM_SECRET_AGENT_GET_SECRETS_FLAG_REQUEST_NEW

explicitly prompt for new -secrets from the user. This flag signals that NetworkManager thinks any -existing secrets are invalid or wrong. This flag implies that interaction -is allowed.

+ secrets from the user. This flag signals that NetworkManager thinks any + existing secrets are invalid or wrong. This flag implies that interaction + is allowed.

@@ -2785,9 +2785,9 @@ is allowed.

NM_SECRET_AGENT_GET_SECRETS_FLAG_USER_REQUESTED

set if the request was -initiated by user-requested action via the D-Bus interface, as opposed to -automatically initiated by NetworkManager in response to (for example) scan -results or carrier changes.

+ initiated by user-requested action via the D-Bus interface, as opposed to + automatically initiated by NetworkManager in response to (for example) scan + results or carrier changes.

@@ -2795,8 +2795,8 @@ results or carrier changes.

NM_SECRET_AGENT_GET_SECRETS_FLAG_WPS_PBC_ACTIVE

indicates that WPS enrollment -is active with PBC method. The agent may suggest that the user pushes a button -on the router instead of supplying a PSK.

+ is active with PBC method. The agent may suggest that the user pushes a button + on the router instead of supplying a PSK.

@@ -2804,7 +2804,7 @@ on the router instead of supplying a PSK.

NM_SECRET_AGENT_GET_SECRETS_FLAG_ONLY_SYSTEM

Internal flag, not part of -the D-Bus API.

+ the D-Bus API.

@@ -2812,7 +2812,7 @@ the D-Bus API.

NM_SECRET_AGENT_GET_SECRETS_FLAG_NO_ERRORS

Internal flag, not part of -the D-Bus API.

+ the D-Bus API.

@@ -3123,7 +3123,7 @@ VPN plugin authentication dialogs.

NM_CHECKPOINT_CREATE_FLAG_DESTROY_ALL

when creating -a new checkpoint, destroy all existing ones.

+ a new checkpoint, destroy all existing ones.

@@ -3131,7 +3131,7 @@ a new checkpoint, destroy all existing ones.

NM_CHECKPOINT_CREATE_FLAG_DELETE_NEW_CONNECTIONS

upon rollback, -delete any new connection added after the checkpoint (Since: 1.6)

+ delete any new connection added after the checkpoint (Since: 1.6)

@@ -3139,7 +3139,7 @@ delete any new connection added after the checkpoint (Since: 1.6)

NM_CHECKPOINT_CREATE_FLAG_DISCONNECT_NEW_DEVICES

upon rollback, -disconnect any new device appeared after the checkpoint (Since: 1.6)

+ disconnect any new device appeared after the checkpoint (Since: 1.6)

@@ -3147,17 +3147,17 @@ disconnect any new device appeared after the checkpoint (Since: 1.6)

NM_CHECKPOINT_CREATE_FLAG_ALLOW_OVERLAPPING

by default, creating -a checkpoint fails if there are already existing checkoints that -reference the same devices. With this flag, creation of such -checkpoints is allowed, however, if an older checkpoint -that references overlapping devices gets rolled back, it will -automatically destroy this checkpoint during rollback. This -allows to create several overlapping checkpoints in parallel, -and rollback to them at will. With the special case that -rolling back to an older checkpoint will invalidate all -overlapping younger checkpoints. This opts-in that the -checkpoint can be automatically destroyed by the rollback -of an older checkpoint. (Since: 1.12)

+ a checkpoint fails if there are already existing checkoints that + reference the same devices. With this flag, creation of such + checkpoints is allowed, however, if an older checkpoint + that references overlapping devices gets rolled back, it will + automatically destroy this checkpoint during rollback. This + allows to create several overlapping checkpoints in parallel, + and rollback to them at will. With the special case that + rolling back to an older checkpoint will invalidate all + overlapping younger checkpoints. This opts-in that the + checkpoint can be automatically destroyed by the rollback + of an older checkpoint. (Since: 1.12)

@@ -3236,9 +3236,9 @@ of an older checkpoint. (Since: 1.12)

NM_SETTINGS_CONNECTION_FLAG_UNSAVED

the connection is not saved to disk. -That either means, that the connection is in-memory only and currently -is not backed by a file. Or, that the connection is backed by a file, -but has modifications in-memory that were not persisted to disk.

+ That either means, that the connection is in-memory only and currently + is not backed by a file. Or, that the connection is backed by a file, + but has modifications in-memory that were not persisted to disk.

@@ -3246,9 +3246,9 @@ but has modifications in-memory that were not persisted to disk.

NM_SETTINGS_CONNECTION_FLAG_NM_GENERATED

A connection is "nm-generated" if -it was generated by NetworkManger. If the connection gets modified or saved -by the user, the flag gets cleared. A nm-generated is also unsaved -and has no backing file as it is in-memory only.

+ it was generated by NetworkManger. If the connection gets modified or saved + by the user, the flag gets cleared. A nm-generated is also unsaved + and has no backing file as it is in-memory only.

@@ -3256,10 +3256,10 @@ and has no backing file as it is in-memory only.

NM_SETTINGS_CONNECTION_FLAG_VOLATILE

The connection will be deleted -when it disconnects. That is for in-memory connections (unsaved), which are -currently active but deleted on disconnect. Volatile connections are -always unsaved, but they are also no backing file on disk and are entirely -in-memory only.

+ when it disconnects. That is for in-memory connections (unsaved), which are + currently active but deleted on disconnect. Volatile connections are + always unsaved, but they are also no backing file on disk and are entirely + in-memory only.

@@ -3327,7 +3327,7 @@ in-memory only.

NM_ACTIVATION_STATE_FLAG_MASTER_HAS_SLAVES

The master has any slave devices attached. -This only makes sense if the device is a master.

+ This only makes sense if the device is a master.

@@ -3335,9 +3335,9 @@ This only makes sense if the device is a master.

NM_ACTIVATION_STATE_FLAG_LIFETIME_BOUND_TO_PROFILE_VISIBILITY

the lifetime -of the activation is bound to the visilibity of the connection profile, -which in turn depends on "connection.permissions" and whether a session -for the user exists. Since: 1.16

+ of the activation is bound to the visilibity of the connection profile, + which in turn depends on "connection.permissions" and whether a session + for the user exists. Since: 1.16

@@ -3384,9 +3384,9 @@ for the user exists. Since: 1.16

NM_SETTINGS_ADD_CONNECTION2_FLAG_BLOCK_AUTOCONNECT

usually, when the connection -has autoconnect enabled and gets added, it becomes eligible to autoconnect -right away. Setting this flag, disables autoconnect until the connection -is manually activated.

+ has autoconnect enabled and gets added, it becomes eligible to autoconnect + right away. Setting this flag, disables autoconnect until the connection + is manually activated.

@@ -3425,16 +3425,16 @@ is manually activated.

NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY

makes the profile in-memory. -Note that such profiles are stored in keyfile format under /run. -If the file is already in-memory, the file in /run is updated in-place. -Otherwise, the previous storage for the profile is left unchanged -on disk, and the in-memory copy shadows it. -Note that the original filename of the previous persistent storage (if any) -is remembered. That means, when later persisting the profile again to disk, -the file on disk will be overwritten again. -Likewise, when finally deleting the profile, both the storage from /run -and persistent storage are deleted (or if the persistent storage does not -allow deletion, and nmmeta file is written to mark the UUID as deleted).

+ Note that such profiles are stored in keyfile format under /run. + If the file is already in-memory, the file in /run is updated in-place. + Otherwise, the previous storage for the profile is left unchanged + on disk, and the in-memory copy shadows it. + Note that the original filename of the previous persistent storage (if any) + is remembered. That means, when later persisting the profile again to disk, + the file on disk will be overwritten again. + Likewise, when finally deleting the profile, both the storage from /run + and persistent storage are deleted (or if the persistent storage does not + allow deletion, and nmmeta file is written to mark the UUID as deleted).

@@ -3442,12 +3442,12 @@ allow deletion, and nmmeta file is written to mark the UUID as deleted).

NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY_DETACHED

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.

+ 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.

@@ -3455,9 +3455,9 @@ storage is taken over again.

NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY_ONLY

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.

+ 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.

@@ -3465,14 +3465,14 @@ a new, unused filename will be chosen.

NM_SETTINGS_UPDATE2_FLAG_VOLATILE

This can be specified with either -NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY, NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY_DETACHED -or NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY_ONLY. -After making the connection in-memory only, the connection is marked -as volatile. That means, if the connection is currently not active -it will be deleted right away. Otherwise, it is marked to for deletion -once the connection deactivates. A volatile connection cannot autoactivate -again (because it's about to be deleted), but a manual activation will -clear the volatile flag.

+ NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY, NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY_DETACHED + or NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY_ONLY. + After making the connection in-memory only, the connection is marked + as volatile. That means, if the connection is currently not active + it will be deleted right away. Otherwise, it is marked to for deletion + once the connection deactivates. A volatile connection cannot autoactivate + again (because it's about to be deleted), but a manual activation will + clear the volatile flag.

@@ -3480,9 +3480,9 @@ clear the volatile flag.

NM_SETTINGS_UPDATE2_FLAG_BLOCK_AUTOCONNECT

usually, when the connection -has autoconnect enabled and is modified, it becomes eligible to autoconnect -right away. Setting this flag, disables autoconnect until the connection -is manually activated.

+ has autoconnect enabled and is modified, it becomes eligible to autoconnect + right away. Setting this flag, disables autoconnect until the connection + is manually activated.

@@ -3490,12 +3490,12 @@ is manually activated.

NM_SETTINGS_UPDATE2_FLAG_NO_REAPPLY

when a profile gets modified that is -currently active, then these changes don't take effect for the active -device unless the profile gets reactivated or the configuration reapplied. -There are two exceptions: by default "connection.zone" and "connection.metered" -properties take effect immediately. Specify this flag to prevent these -properties to take effect, so that the change is restricted to modify -the profile. Since: 1.20.

+ currently active, then these changes don't take effect for the active + device unless the profile gets reactivated or the configuration reapplied. + There are two exceptions: by default "connection.zone" and "connection.metered" + properties take effect immediately. Specify this flag to prevent these + properties to take effect, so that the change is restricted to modify + the profile. Since: 1.20.

@@ -3546,6 +3546,6 @@ the profile. Since: 1.20.

Generated by GTK-Doc V1.29 \ No newline at end of file -- cgit 1.3.0-6-gf8a5