public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: resolv.conf full of old info
Date: Wed, 19 Oct 2022 10:22:05 +0100	[thread overview]
Message-ID: <5871429.lOV4Wx5bFT@lenovo.localdomain> (raw)
In-Reply-To: <tinemv$ula$1@ciao.gmane.io>

[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]

On Wednesday, 19 October 2022 01:00:31 BST Grant Edwards wrote:
> 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

I think because this causes less breakage in those cases where netmount, 
remote syslog-ng, SSH clients, or root mounted NFS is in play?  This is what 
the man page says about it:

"... dhcpcd normally de-configures the interface and configuration when it 
exits.  Sometimes, this isn't desirable if, for example, you have root mounted 
over NFS or SSH clients connect to this host and they need to be notified of 
the host shutting down."

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-10-19  9:22 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 ` [gentoo-user] " Grant Edwards
2022-10-19  9:22   ` Michael [this message]
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=5871429.lOV4Wx5bFT@lenovo.localdomain \
    --to=confabulate@kintzios.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