> I've got a loopback mount in /var/db/mounttab that looks like this:
>
> 946789037 localhost /null
>
> which is there because I run cfs (a crypto file system; see
> /usr/ports/security/cfs). Part of the cfs startup script does
> this:
>
> /usr/local/sbin/cfsd && mount -o port=3049,intr localhost:/null /crypt
>
> The problem is that when you boot, the invocation of 'rpc.umntall -k'
> hangs for a while trying to contact the mountd or portmapper on localhost.
> If it was smart enough to recognize an ICMP port unreachable error and
> move on, we wouldn't have this problem.
>
> It's not that I think moving mountd and portmap is necessarily a good
> idea; this is just one scenario which perhaps has prompted this line of
That's because rpc.umntall has been called the wrong time. I have
another patch which does fix this behaviour.
Thanks anyway.
BTW: you cannot have this line in /etc/fstab, right ? If you put
localhost:/null /crypt in fstab, you will get a hang at boottime.
Are there other cases for which we will have problems ?
Martin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
