From 45cb5bb3c0e6edb887cf69b417fcaf7053814a9b Mon Sep 17 00:00:00 2001 From: Aron Xu Date: Tue, 20 Dec 2016 20:06:37 +0800 Subject: Imported Upstream version 1.4.4 --- docs/api/html/NetworkManager.html | 44 +++++++++++++++++++++++++-------------- 1 file changed, 28 insertions(+), 16 deletions(-) (limited to 'docs/api/html/NetworkManager.html') diff --git a/docs/api/html/NetworkManager.html b/docs/api/html/NetworkManager.html index 10704589..3fa72590 100644 --- a/docs/api/html/NetworkManager.html +++ b/docs/api/html/NetworkManager.html @@ -3,7 +3,7 @@ NetworkManager: NetworkManager Reference Manual - + @@ -51,7 +51,8 @@

Dispatcher scripts

NetworkManager will execute scripts in the - /etc/NetworkManager/dispatcher.d directory or subdirectories in + /etc/NetworkManager/dispatcher.d + directory or subdirectories in alphabetical order in response to network events. Each script should be a regular executable file owned by root. Furthermore, it must not be writable by group or other, and not setuid. @@ -75,8 +76,8 @@

pre-up

The interface is connected to the network but is not yet fully activated. Scripts acting on this event must be placed or - symlinked into the /etc/NetworkManager/dispatcher.d/pre-up.d directory, - and NetworkManager will wait for script execution to complete before + symlinked into the /etc/NetworkManager/dispatcher.d/pre-up.d + directory, and NetworkManager will wait for script execution to complete before indicating to applications that the interface is fully activated.

@@ -88,7 +89,7 @@

pre-down

The interface will be deactivated but has not yet been disconnected from the network. Scripts acting on this event must be - placed or symlinked into the /etc/NetworkManager/dispatcher.d/pre-down.d + placed or symlinked into the /etc/NetworkManager/dispatcher.d/pre-down.d directory, and NetworkManager will wait for script execution to complete before disconnecting the interface from its network. Note that this event is not emitted for forced disconnections, like when carrier is @@ -106,8 +107,8 @@

vpn-pre-up

The VPN is connected to the network but is not yet fully activated. Scripts acting on this event must be placed or - symlinked into the /etc/NetworkManager/dispatcher.d/pre-up.d directory, - and NetworkManager will wait for script execution to complete before + symlinked into the /etc/NetworkManager/dispatcher.d/pre-up.d + directory, and NetworkManager will wait for script execution to complete before indicating to applications that the VPN is fully activated.

@@ -121,7 +122,7 @@

vpn-pre-down

The VPN will be deactivated but has not yet been disconnected from the network. Scripts acting on this event must be - placed or symlinked into the /etc/NetworkManager/dispatcher.d/pre-down.d + placed or symlinked into the /etc/NetworkManager/dispatcher.d/pre-down.d directory, and NetworkManager will wait for script execution to complete before disconnecting the VPN from its network. Note that this event is not emitted for forced disconnections, like when the VPN @@ -304,7 +305,8 @@ NetworkManager process, and will be killed if they run for too long. If your script might take arbitrarily long to complete, you should spawn a child process and have the parent return immediately. Scripts that are symbolic links pointing inside the - /etc/NetworkManager/dispatcher.d/no-wait.d/ directory are run immediately, without + /etc/NetworkManager/dispatcher.d/no-wait.d/ + directory are run immediately, without waiting for the termination of previous scripts, and in parallel. Also beware that once a script is queued, it will always be run, even if a later event renders it obsolete. (Eg, if an interface goes up, and then back down again quickly, it is @@ -352,14 +354,16 @@

--state-file

Specify file for storing state of the NetworkManager persistently. If not specified, the default - value of /var/lib/NetworkManager/NetworkManager.state is used. + value of /var/lib/NetworkManager/NetworkManager.state + is used.

--config

Specify configuration file to set up various settings for NetworkManager. If not specified, the default - value of /etc/NetworkManager/NetworkManager.conf is used with + value of /etc/NetworkManager/NetworkManager.conf + is used with a fallback to the older 'nm-system-settings.conf' if located in the same directory. See NetworkManager.conf(5) @@ -405,7 +409,7 @@

-

UDEV PROPERTIES

+

Udev Properties

udev(7) device manager is used for the network device discovery. The following @@ -456,8 +460,8 @@ A SIGHUP also involves further reloading actions, like doing a DNS update and restarting the DNS plugin. The latter can be useful for example when using the dnsmasq plugin and changing - its configuration in /etc/NetworkManager/dnsmasq.d. However, - it also means this will shortly interrupt name resolution. + its configuration in /etc/NetworkManager/dnsmasq.d. + However, it also means this will shortly interrupt name resolution. In the future, there may be further actions added. A SIGHUP means to update NetworkManager configuration and reload everything that is supported. Note that this does not reload @@ -495,7 +499,7 @@

-

DEBUGGING

+

Debugging

The following environment variables are supported to help debugging. When used in conjunction with the @@ -512,8 +516,16 @@

-

See Also

+

Bugs

+ Please report any bugs you find in NetworkManager at the + NetworkManager bug tracker. +

+
+
+

See Also

+

+ NetworkManager home page, NetworkManager.conf(5), nmcli(1), nmcli-examples(7), -- cgit 1.3.0-6-gf8a5