Date: Sun, 29 Nov 2009 20:34:00 +0100 From: Harald Schmalzbauer <h.schmalzbauer@omnilan.de> To: freebsd-current@freebsd.org Subject: named, VARMFS=yes and FILESDIR Message-ID: <4B12CCA8.7050808@omnilan.de>
next in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig8FACEF62C489845756297F80
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: quoted-printable
Hello,
while building an embedded slave DNS I recognized that running named out =
of the box with VARMFS enabled would fail.
Now I could easily fix it for my device only, but I think it's better to =
solve it upstream.
VARMFS=3DYes is a standard option, likewise named_enable.
Short description of the problem:
When rc detects non-writabel /var or VARMFS is set to yes, a new /var=20
tree gets populated. This comes without config, hint file and likewise=20
for /var/named/namedb, but /etc/namedb is a symlink to /var/named/namedb.=
rc.d/named could easily be supplemented with the neccessary checks, but=20
we don't have the needed files outside of /var.
My idea is to create a namedb directory in /usr/share (like there's one=20
for sendmail) with duplicate entries of src/etc/namedb
Unfortunately I couldn't find out where FILESDIR is processed in the bsd =
build stages.
If the idea is plausable, how do I best install /usr/share/namedb?
src/etc/namedb is entered at DISTRIBUTION target, right?
Id highly appreciate if somebody who's familar with the build stages=20
could give me some hints.
Thanks,
-Harry
P.S.: named_conf definitions in rc.conf get lost. Here's the patch:
--- etc/rc.d/named.orig 2009-09-13 20:11:34.000000000 +0200
+++ etc/rc.d/named 2009-09-13 21:38:29.000000000 +0200
@@ -264,6 +284,6 @@
#
required_dirs=3D"$named_chrootdir" # if it is set, it must exist
pidfile=3D"${named_pidfile:-/var/run/named/pid}"
-command_args=3D"-u ${named_uid:=3Droot}"
+command_args=3D"-c $named_conf -u ${named_uid:=3Droot}"
--------------enig8FACEF62C489845756297F80
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.13 (FreeBSD)
iEYEARECAAYFAksSzK8ACgkQLDqVQ9VXb8iOegCfQ/HP+m8qcvXjasaKGZ/LlCOB
VMcAoK6paCjU5hupBHMoJhhbrqwez7GG
=hY+j
-----END PGP SIGNATURE-----
--------------enig8FACEF62C489845756297F80--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B12CCA8.7050808>