diff options
| author | Michael Biebl <biebl@debian.org> | 2022-10-04 00:56:46 +0200 |
|---|---|---|
| committer | Michael Biebl <biebl@debian.org> | 2022-10-04 00:56:46 +0200 |
| commit | 3612e6355f3f40d264ec4657547761069baa5430 (patch) | |
| tree | 768e4f5b37b66f540dd7030aa2eaff2ac7bb0168 /man/NetworkManager-wait-online.service.xml | |
| parent | 7e9f00a3be8f65535e6620b344443ec4d403212b (diff) | |
| parent | 6f7fcde10e47d8af865af336becf1fd8a446e62e (diff) | |
Merge tag 'debian/1.40.0-1' into debian/bullseye-backports
network-manager Debian release 1.40.0-1
Diffstat (limited to 'man/NetworkManager-wait-online.service.xml')
| -rw-r--r-- | man/NetworkManager-wait-online.service.xml | 25 |
1 files changed, 24 insertions, 1 deletions
diff --git a/man/NetworkManager-wait-online.service.xml b/man/NetworkManager-wait-online.service.xml index d061643c..9bc947e5 100644 --- a/man/NetworkManager-wait-online.service.xml +++ b/man/NetworkManager-wait-online.service.xml @@ -95,6 +95,11 @@ setting). While trying and retrying, NetworkManager is busy until all profiles and devices either reached an activated or disconnected state and no further events are expected. + <para> + </para> + Basically, as long as there are devices and connections in <literal>activating</literal> + state visible with <command>nmcli device</command> and <command>nmcli connection</command>, + startup is still pending. </para> </listitem> <listitem> @@ -122,9 +127,27 @@ </listitem> <listitem> <para> + Dispatcher scripts for the "pre-up" event run at a late stage during activation + of a profile. These scripts block the activation for when NetworkManager considers + the profile fully activated. + See also <link linkend='NetworkManager-dispatcher'><citerefentry><refentrytitle>NetworkManager-dispatcher</refentrytitle><manvolnum>8</manvolnum></citerefentry></link> + for details. + </para> + </listitem> + <listitem> + <para> + The connection property <literal>connection.wait-activation-delay</literal> also + adds an additional delay during activation and delays startup complete. This is to + workaround certain cases where a device is known to not be ready for a certain + amount of time. + </para> + </listitem> + <listitem> + <para> The property <literal>connection.wait-device-timeout</literal> of the connection profiles waits until the waited devices appear. This is useful if the driver - takes a longer time to detect the networking interfaces. + takes a longer time to detect the networking interfaces. Similar with the + <literal>connection.gateway-ping-timeout</literal> property. </para> </listitem> <listitem> |