rc.d/mountd: confusing message (and behavior?)

Garrett Cooper yanefbsd at gmail.com
Sat Jan 10 07:16:56 PST 2009


On Sat, Jan 10, 2009 at 7:14 AM, Andriy Gapon <avg at icyb.net.ua> wrote:
> on 10/01/2009 17:11 Garrett Cooper said the following:
>> On Sat, Jan 10, 2009 at 6:20 AM, Andriy Gapon <avg at 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...
>
> I thought that mountd and nfsd (and rpcbind) are still required even if
> exported filesystems are ZFS. Am I wrong on 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 at 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

Ok, dumb question -- does ZFS offer the same functionality as NFS? I
thought not...
-Garrett


More information about the freebsd-stable mailing list