Date: Wed, 18 Jan 2023 07:51:37 -0800 (PST) From: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net> To: Juraj Lutter <otis@freebsd.org> Cc: "Rodney W. Grimes" <rgrimes@freebsd.org>, Cy Schubert <Cy.Schubert@cschubert.com>, src-committers@freebsd.org, dev-commits-src-all@freebsd.org, dev-commits-src-main@freebsd.org Subject: Re: git: 1d577bedbae8 - main - unbound: Fix config file path Message-ID: <202301181551.30IFpbRu010474@gndrsh.dnsmgr.net> In-Reply-To: <459C4261-C860-4761-98AC-8F9B867BA918@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[ Charset UTF-8 unsupported, converting... ] > > > > On 18 Jan 2023, at 16:34, Rodney W. Grimes <freebsd@gndrsh.dnsmgr.net> wrote: > > > > No, otis fixed it thus: > > -#define CONFIGFILE "/usr/local/etc/unbound/unbound.conf" > > +#define CONFIGFILE "/var/unbound/unbound.conf" > > > > > > I am suggesting that it should be > > #define CONFIGFILE "/etc/unbound/unbound.conf" > > > > ALL base system configuration files *should* be relative to /etc, not /var. > > > > Would this need any mtree changes or similar? No, /etc/unbound is a symbolic link already installed by the build system, and /var/unbound is already a directory, again, installed by the build system. This is a one line change that actually makes the /etc/unbound link work correctly, without this change the binary has a hard coded path that ignores the /etc/unbound symbolic link and requires a recompile if I want to move things around, or maintanance of 2 symbolic links. Personally I dont see *why* unbound has a /var/unbound directory, can someone tell me why that was done? Is this some attempt and maintaining read only root? Does unbound scribble in the config directory, or is this simply mirroring some of the stuff that bind did? > ? > Juraj Lutter > otis@FreeBSD.org -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202301181551.30IFpbRu010474>