On Tuesday 10 February 2009 01:34:47 Arjan van der Oest wrote:
> Hi Mel,
>
> Sorry for not getting back to you earlier, I have been out of the office
> for some time...
>
> > Does this one also have a link UP message after nfs mounting? If not,
>
> then
>
> > there's your culprit: network isn't up
Hi Mel,
Sorry for not getting back to you earlier, I have been out of the office
for some time...
> Does this one also have a link UP message after nfs mounting? If not,
then
> there's your culprit: network isn't up at mountcritremote time. You
should
> mark it 'late' in fstab
The UP message ca
On Friday 30 January 2009 04:36:04 Arjan van der Oest wrote:
> Mel wrote:
> >> - why does the system tries to mount the nfs filesystem from the
>
> fstab
>
> >> while nfs_client_enable has been set to no in rc.conf?
> >
> >Because there is no relation between the two. You could be using a 3rd
> >pa
Mel wrote:
>> - why does the system tries to mount the nfs filesystem from the
fstab
>> while nfs_client_enable has been set to no in rc.conf?
>Because there is no relation between the two. You could be using a 3rd
>party nfs kernel module.
Yes, but I am not. I'm using the default kernel option w
On Thursday 29 January 2009 00:47:49 Arjan van der Oest wrote:
> Hi,
>
> I’m puzzled and either I don’t understand the boot rc.d process or there is
> something wrong with it ☺
>
> I have this 7.1-RELEASE-p2 amd64 machine compiled with a GENERIC kernel, so
> NFS support is baked right into the kern
