[PATCH] doc: Update connman(8) manpage on the --nodnsproxy option.

[PATCH] doc: Update connman(8) manpage on the --nodnsproxy option.

[Oskar Roesler (bionade24)]

From: "Oskar Roesler" <o.roesler@oscloud.info>

The --nodnsproxy option documentation left out that ConnMan will fall
back to creating a resolv.conf on startup. This gets fixed by this.
---
 doc/connman.8.in | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/doc/connman.8.in b/doc/connman.8.in
index 85e7c5e0..868196c3 100644
--- a/doc/connman.8.in
+++ b/doc/connman.8.in
@@ -94,9 +94,11 @@ to itself by setting nameserver to 127.0.0.1 in \fBresolv.conf\fP(5)
 file or leave DNS management to an external entity, such as
 systemd-resolved. If this is not desired and you want that all programs
 call directly some DNS server, then you can use the \fB--nodnsproxy\fP
-option. If this option is used, then ConnMan is not able to cache the
-DNS queries because the DNS traffic is not going through ConnMan and that
-can cause some extra network traffic.
+option. ConnMan then figures out the DNS server and search domain
+on startup and sets them in \fBresolv.conf\fP(5). If this option is
+used, then ConnMan is not able to cache the DNS queries because the DNS
+traffic is not going through ConnMan and that can cause some extra
+network traffic.
 .SH SEE ALSO
 .BR connmanctl (1), \ connman.conf (5), \ connman-service.config (5), \c
 .BR \ connman-vpn (8)
-- 
2.39.1

Re: [PATCH] doc: Update connman(8) manpage on the --nodnsproxy option.

[Daniel Wagner]

On Tue, 21 Feb 2023 01:20:10 +0100, Oskar Roesler (bionade24) wrote:
> The --nodnsproxy option documentation left out that ConnMan will fall
> back to creating a resolv.conf on startup. This gets fixed by this.
> 

Applied, thanks!

[1/1] doc: Update connman(8) manpage on the --nodnsproxy option.
      commit: 9cf2cc3844e486a81c5c118de4bcbde3489e097a

Best regards,
-- 
Daniel Wagner <wagi@monom.org>