Date: Tue, 18 Oct 2022 16:53:40 -0600 From: Bob Proulx <bob@proulx.com> To: freebsd-questions@freebsd.org Subject: Re: resolv.conf question Message-ID: <20221018165212N@bob.proulx.com> In-Reply-To: <Y08Su%2BysnXYOMSYA@lorvorc.mips.inka.de> References: <alpine.BSF.2.00.2210111300120.66282@bucksport.safeport.com> <CAFbbPug83%2BxyjZoR%2BOZ1HqnzDCptmqLFbZ7vThgP9=O6QjF-KA@mail.gmail.com> <alpine.BSF.2.00.2210111630040.66282@bucksport.safeport.com> <20221012185254621820516@bob.proulx.com> <7F000833-031D-41D9-8C49-F999F1A9AD73@gushi.org> <20221013102456085799804@bob.proulx.com> <Y08Su%2BysnXYOMSYA@lorvorc.mips.inka.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Christian Weisgerber wrote: > Bob Proulx: > > And also note that the resolver only reads resolv.conf at start up > > time. Meaning that if changes are made any programs using it must be > > restarted. > > Actually, this was improved seven years ago. I'll just quote from > resolver(5): > > reload-period:n > The resolver checks the modification time of > /etc/resolv.conf every n seconds. If > /etc/resolv.conf has changed, it is > automatically reloaded. The default for n is > two seconds. Setting it to zero disables the > file check. Woot! :-) Bob
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20221018165212N>