From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 8FEBD158020 for ; Wed, 19 Oct 2022 00:00:46 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E3912E08A0; Wed, 19 Oct 2022 00:00:40 +0000 (UTC) Received: from ciao.gmane.io (ciao.gmane.io [116.202.254.214]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id CBB79E0894 for ; Wed, 19 Oct 2022 00:00:38 +0000 (UTC) Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1okwVg-0008IY-1q for gentoo-user@lists.gentoo.org; Wed, 19 Oct 2022 02:00:36 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: Grant Edwards Subject: [gentoo-user] Re: resolv.conf full of old info Date: Wed, 19 Oct 2022 00:00:31 -0000 (UTC) Message-ID: References: User-Agent: slrn/1.0.3 (Linux) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply X-Archives-Salt: c26001fe-fb32-4dd7-acf8-b768ee90b984 X-Archives-Hash: f5dc298a1d03ebbba84a912ce39f312a On 2022-10-18, Grant Edwards 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