On 7 Oct 2002, Gordon Messmer wrote:
> Portmap is required on the client for rpc.statd and rpc.lockd.
You're right. Well, I'll be dipped in stock options. Thanks for the
explaination, Gordon.
--
"The only thing that helps me maintain my slender grip on reality is the
friendship I share with m
On Mon, 2002-10-07 at 13:29, Todd A. Jacobs wrote:
>
> Turns out it was some kind of weirdness with portmap on the *client* side.
> Portmap shouldn't be required on the client, but starting portmapper there
> solved the problem.
Portmap is required on the client for rpc.statd and rpc.lockd.
On 7 Oct 2002, Gordon Messmer wrote:
> Install a newer version of "mount" on the client? Get the one from 7.3
> and see if that corrects the problem. I'd thought that was required,
> but I don't see an errata package for mount on RH's site.
Turns out it was some kind of weirdness with portmap
On Mon, 2002-10-07 at 01:30, Todd A. Jacobs wrote:
> The client-side logs then have this to say:
> Oct 7 01:19:54 gateway kernel: nfs warning: mount version older than kernel
> Any ideas or suggestions?
Install a newer version of "mount" on the client? Get the one from 7.3
and see if that c
I'm trying to mount an NFS share from a Red Hat 8.0 box. The share is a
reiserfs partition. From the logs on the NFS server, rpc.mountd is being
called correctly, but I get the following error from the client:
mount: wrong fs type, bad option, bad superblock on
204.16.1.137:/mnt
