diff options
| author | Beniamino Galvani <bgalvani@redhat.com> | 2021-04-29 10:40:27 +0200 |
|---|---|---|
| committer | Beniamino Galvani <bgalvani@redhat.com> | 2021-05-03 22:13:36 +0200 |
| commit | fa1f628bce9f82bd4c753d75709203c72fff310c (patch) | |
| tree | f1ce6b43e51bde7760c2a46d35bd04b8bfe2ba8d /man | |
| parent | caea7514cb74714077fd372c7264c9582d884c1f (diff) | |
core: force emission of DNS_CONFIG_CHANGED signal on SIGUSR1
If the configuration contains dns=none and resolv.conf is updated
through a dispatcher script, currently there is no way to tell NM that
the content of resolv.conf changed, so that it can restart a hostname
resolution.
Use SIGUSR1 (and SIGHUP) for that.
Diffstat (limited to 'man')
| -rw-r--r-- | man/NetworkManager.xml | 14 |
1 files changed, 11 insertions, 3 deletions
diff --git a/man/NetworkManager.xml b/man/NetworkManager.xml index 8977ae4eed..0092a44f7d 100644 --- a/man/NetworkManager.xml +++ b/man/NetworkManager.xml @@ -224,9 +224,17 @@ <varlistentry> <term><varname>SIGUSR1</varname></term> <listitem><para> - 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 |