From: "Oskar Roesler (bionade24)" <o.roesler@oscloud.info>
To: connman@lists.linux.dev
Cc: "Oskar Roesler" <o.roesler@oscloud.info>
Subject: [PATCH] doc: Update connman(8) manpage on the --nodnsproxy option.
Date: Tue, 21 Feb 2023 01:20:10 +0100 [thread overview]
Message-ID: <20230221002009.253059-1-o.roesler@oscloud.info> (raw)
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
next reply other threads:[~2023-02-21 0:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 0:20 Oskar Roesler (bionade24) [this message]
2023-04-11 7:40 ` [PATCH] doc: Update connman(8) manpage on the --nodnsproxy option Daniel Wagner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230221002009.253059-1-o.roesler@oscloud.info \
--to=o.roesler@oscloud.info \
--cc=connman@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).