Date: Fri, 21 Jun 2019 19:52:39 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 238753] /etc/rc.d/local_unbound fails to honor configuration directory setting pre-start Message-ID: <bug-238753-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238753 Bug ID: 238753 Summary: /etc/rc.d/local_unbound fails to honor configuration directory setting pre-start Product: Base System Version: 12.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: conf Assignee: bugs@FreeBSD.org Reporter: karl@denninger.net Created attachment 205269 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D205269&action= =3Dedit Address missing "-c" flag on the control command /etc/rc.d/local_unbound starts the local "unbound" nameserver. The script assumes the working directory is in /var/unbound, which is valid= for most users. However, in an embedded environment /var is frequently on a ramdisk and not saved (that is, it's volatile), which means you need to move this directory for those environments since otherwise you will be regenerat= ing the configuration on each boot -- and that is probably not desirable. The base RC script is intended to honor local_unbound_workdir in /etc/rc.co= nf, but the "local_unbound_poststart()" function makes a call to the "-control" software without specifying the config directory explicitly with "-c". If = the working directory is not in the default location this results in that comma= nd failing; this is not fatal since the test gives up after five tries, but it should honor the config directive and thus know when the startup has comple= ted successfully. The attached patch adds the "-c" flag to the control command and resolves t= he issue. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-238753-227>