Date: Sat, 10 Jan 2009 07:11:36 -0800 From: "Garrett Cooper" <yanefbsd@gmail.com> To: "Andriy Gapon" <avg@icyb.net.ua> Cc: FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: rc.d/mountd: confusing message (and behavior?) Message-ID: <7d6fde3d0901100711p70e9a66ahadc3c2570fc6f94b@mail.gmail.com> In-Reply-To: <4968AE90.5010004@icyb.net.ua> References: <4968AE90.5010004@icyb.net.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jan 10, 2009 at 6:20 AM, Andriy Gapon <avg@icyb.net.ua> wrote:
>
> $ /etc/rc.d/mountd onestart
> /etc/rc.d/mountd: WARNING: /etc/exports is not readable.
> Exit 1
>
> Actually /etc/exports did not exist at all.
> And this was not a "WARNING", this was a fatal error, mountd did not start.
>
> Alsp, should it actually fail like this? I have ZFS and I plan to do
> all NFS exports from ZFS, so /etc/exports would never be used.
Uh, mountd is used for nfsd, so I'm not sure why you're trying to do
this... The reference to /etc/exports is being picked up from
/etc/rc.d/mountd on this line:
required_files="/etc/exports"
and it's picking up the actual `does it exist?' test from:
[gcooper@orangebox /usr/home/gcooper]$ grep -A 3 required_files /etc/rc.subr
# required_files n If set, check for the readability of the given
# files before running a (re)start command.
#
# required_modules n If set, ensure the given kernel modules are
--
rcvar required_dirs required_files required_vars
eval unset ${_arg}_cmd ${_arg}_precmd ${_arg}_postcmd
case "$_file" in
--
for _f in $required_files; do
if [ ! -r "${_f}" ]; then
warn "${_f} is not readable."
if [ -z "$rc_force" ]; then
Cheers,
-Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7d6fde3d0901100711p70e9a66ahadc3c2570fc6f94b>