From bfe522304da217296e2a61040f58e35ec5d6f3f2 Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Mon, 16 Aug 2021 09:51:46 +0200 Subject: New upstream version 1.30.6 --- docs/api/html/NetworkManager.html | 18 +++++++++++++----- 1 file changed, 13 insertions(+), 5 deletions(-) (limited to 'docs/api/html/NetworkManager.html') diff --git a/docs/api/html/NetworkManager.html b/docs/api/html/NetworkManager.html index ff497a1c..9bfcd4e3 100644 --- a/docs/api/html/NetworkManager.html +++ b/docs/api/html/NetworkManager.html @@ -8,7 +8,7 @@ - + @@ -479,9 +479,17 @@

SIGUSR1

- The signal forces a rewrite of DNS configuration. Contrary to - SIGHUP, this does not restart the DNS plugin and will not interrupt - name resolution. + The signal forces a rewrite of DNS configuration. Contrary + to SIGHUP, this does not restart the DNS plugin and will not + interrupt name resolution. + + When NetworkManager is not managing DNS, the signal forces + a restart of operations that depend on the DNS + configuration (like the resolution of the system hostname + via reverse DNS, or the resolution of WireGuard peers); + therefore, it can be used to tell NetworkManager that the + content of resolv.conf was changed externally. + In the future, further actions may be added. A SIGUSR1 means to write out data like resolv.conf, or refresh a cache. It is a subset of what is done for SIGHUP without reloading @@ -594,6 +602,6 @@

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