From: Grant Edwards <grant.b.edwards@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: resolv.conf full of old info
Date: Wed, 19 Oct 2022 00:00:31 -0000 (UTC) [thread overview]
Message-ID: <tinemv$ula$1@ciao.gmane.io> (raw)
In-Reply-To: tin8tm$179q$1@ciao.gmane.io
On 2022-10-18, Grant Edwards <grant.b.edwards@gmail.com> wrote:
> I've noticed that /etc/resolv.conf seems to accumulate obsolete,
> useless info as my laptop moves from one network to another. It looks
> like dhcpcd adds stuff when a connection comes up, but never removes
> it when the connection goes down.
This appears to be caused by the "persistent" option in dhcpcd.conf,
which is set by default. I commented it out, and now resolv.conf
behaves rationally: it only contains info for network connections that
are up.
Why would dhcpcd have the persistent option enabled by default?
--
Grant
next prev parent reply other threads:[~2022-10-19 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 22:21 [gentoo-user] resolv.conf full of old info Grant Edwards
2022-10-19 0:00 ` Grant Edwards [this message]
2022-10-19 9:22 ` [gentoo-user] " Michael
2022-10-19 13:39 ` Grant Edwards
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='tinemv$ula$1@ciao.gmane.io' \
--to=grant.b.edwards@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/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