Hi,
I'm having some problems using knfsd with a linux 2.2.6 kernel
(patched with the nfsd-2.2.5-3.patch from the knfsd-1.4 distribution)
and the 'amd' automounter running on Irix or Solaris NFS clients.
Specifically, if I use amd 'host' maps, the nonlinux systems are
unable to use the 'pwd' command to print the name of the current
directory or to use '..' to move up the amd-mounted directory tree.
Trying to do so results in the following messages in /var/log/messages
on the linux NFS server:
SGI IRIX 5.3 CLIENT:
Jun 23 16:52:58 bulwinkle mountd[361]: export request from 192.168.1.8
Jun 23 16:52:58 bulwinkle mountd[361]: authenticated mount request from
rocky.whatsamatta.edu:1023
Jun 23 16:52:58 bulwinkle kernel: fh_verify: /// permission failure, acc=3, error=13
Jun 23 16:53:13 bulwinkle kernel: fh_verify: //usr5 permission failure, acc=1, error=1
SOLARIS 2.5.1 CLIENT:
Jun 23 10:57:54 bulwinkle mountd[361]: export request from 192.168.1.9
Jun 23 10:57:54 bulwinkle mountd[361]: authenticated mount request from
natasha.whatsamatta.edu:1022
Jun 23 10:58:05 bulwinkle kernel: svc: unknown program 100227 (me 100003)
Jun 23 10:58:05 bulwinkle kernel: fh_verify: /// permission failure, acc=3, error=13
Jun 23 10:58:05 bulwinkle kernel: svc: unknown program 100227 (me 100003)
Jun 23 10:58:08 bulwinkle kernel: fh_verify: //usr5 permission failure, acc=1, error=1
The error messages are repeated for each filesystem exported from the
linux server.
Mounting the filesystems by hand or using amd 'nfs' maps works fine.
The same setup works fine with the regular, user-space linux NFS
server. RPC program 100227 is not registered on the user-space NFS
server linux systems, but it doesn't seem to matter.
The amd maps is question look like (the real maps are more complex,
but these will reproduce the problem):
HOST MAP:
* type:=host;rhost:=${key};fs:=${autodir}/${rhost}/root
NET MAP:
pub host!=bulwinkle;type:=nfs;rhost:=bulwinkle;rfs:=/scr/pub \
host==bulwinkle;type:=link;fs:=/scr/pub
Unfortunately, the SGI and Sun systems in question are largely out of
my control, and the folks who manage them are set on continuing to use
'host' maps.
Any ideas? Please send responses directly to me in addition to
responding to the list.
Thanks,
Chance
--
Chance Reschke
Astronomy Department
University of Washington
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
