Disabling NFSv4 on the server?

I have a linux box I need to use as an NFS server for a sun NFS client.

The Sun client is mounting from the linux server from myriad different
places in shell scripts and (hopefully not) C programs.

The communication is having problems when they try to use NFSv4. All
seems fine if they use NFSv3, but there are too many places to add vers=3
to all the mount commands.

So it'd be a lot easier to change the linux server to only advertise that
it can support NFSv3 and v2.

However, I tried deleting NFS 4 and mountd 3 from portmap, and I tried
killing ipmapd, but the pair apparently still want to use NFSv4.

How can I be rid of NFSv4 via a change to the linux (FC4) NFS server?

Thanks!

Dan Stromberg <(E-Mail Removed)> wrote:
> The Sun client is mounting from the linux server from myriad different
> places in shell scripts and (hopefully not) C programs.
> The communication is having problems when they try to use NFSv4. All
> seems fine if they use NFSv3, but there are too many places to add vers=3
> to all the mount commands.

No offense, but if the only way you can change the behavior is by
changing the scripts in "too many places", then you're doing something
wrong at a higher conceptual level. This is why we use things like
/etc/fstab, or an automounter, or config files, or even just variables:
so we can change things once and have them take effect in many places,
instead of having to try and hunt down everywhere that might refer to
something. Still, I realize that these scripts were probably written
years ago, by someone who is no longer available for a beating...


> How can I be rid of NFSv4 via a change to the linux (FC4) NFS server?

Did you look at 'man rpc.mountd'? From the manpage:

-N or --no-nfs-version
This option can be used to request that rpc.mountd do not offer certain
versions of NFS. The current version of rpc.mountd can support both NFS
version 2 and the newer version 3. If the NFS kernel module was
compiled without support for NFSv3, rpc.mountd must be invoked with the
option --no-nfs-version 3 .

I assume it will work to prevent v4 - never tried it.

--
Oh to have a lodge in some vast wilderness. Where rumors of oppression
and deceit, of unsuccessful and successful wars may never reach me
anymore.
-- William Cowper

On Fri, 26 May 2006 15:30:17 +0000, Jeremiah DeWitt Weiner wrote:

> Dan Stromberg <(E-Mail Removed)> wrote:
>> The Sun client is mounting from the linux server from myriad different
>> places in shell scripts and (hopefully not) C programs. The
>> communication is having problems when they try to use NFSv4. All seems
>> fine if they use NFSv3, but there are too many places to add vers=3 to
>> all the mount commands.
>
> No offense, but if the only way you can change the behavior is by
> changing the scripts in "too many places", then you're doing something
> wrong at a higher conceptual level. This is why we use things like
> /etc/fstab, or an automounter, or config files, or even just variables:
> so we can change things once and have them take effect in many places,
> instead of having to try and hunt down everywhere that might refer to
> something. Still, I realize that these scripts were probably written
> years ago, by someone who is no longer available for a beating...

Agreed, but I have 0 authority over that part of this, and it's owned by a
vendor, not my employer.


>> How can I be rid of NFSv4 via a change to the linux (FC4) NFS server?
>
> Did you look at 'man rpc.mountd'? From the manpage:
>
> -N or --no-nfs-version
> This option can be used to request that rpc.mountd do not offer certain
> versions of NFS. The current version of rpc.mountd can support both NFS
> version 2 and the newer version 3. If the NFS kernel module was
> compiled without support for NFSv3, rpc.mountd must be invoked with the
> option --no-nfs-version 3 .
>
> I assume it will work to prevent v4 - never tried it.

Sweet. I'll try that.

Thanks!