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 --- man/NetworkManager.xml | 41 +++++++++++++++++++++++++++-------------- 1 file changed, 27 insertions(+), 14 deletions(-) (limited to 'man/NetworkManager.xml') diff --git a/man/NetworkManager.xml b/man/NetworkManager.xml index 2cb458a2..60dbe7d7 100644 --- a/man/NetworkManager.xml +++ b/man/NetworkManager.xml @@ -69,7 +69,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. @@ -88,8 +89,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. @@ -101,7 +102,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 @@ -119,8 +120,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. @@ -134,7 +135,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 @@ -308,7 +309,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 @@ -354,14 +356,16 @@ 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. 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.conf5 @@ -407,7 +411,7 @@ - UDEV PROPERTIES + Udev Properties udev7 @@ -448,8 +452,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 @@ -486,7 +490,7 @@ - DEBUGGING + Debugging The following environment variables are supported to help debugging. When used in conjunction with the @@ -503,9 +507,18 @@ + + Bugs + + Please report any bugs you find in NetworkManager at the + NetworkManager bug tracker. + + + See Also + NetworkManager home page, NetworkManager.conf5, nmcli1, nmcli-examples7, -- cgit 1.3.0-6-gf8a5