Messages in this thread | | | Subject | Re: [PATCH] access-denied problems with knfsd-981022 | Date | Sat, 31 Oct 1998 20:14:03 -0800 | From | "G. Allen Morris III" <> |
| |
What I think is happening here is that the local system expects to be able to read any file when it is root, and when it is denigned access to a directory it becomes confused.
I will look into the best way to solve this. I assume that the correct response is to always let root (even squashed) to read . and .. in any directory.
Allen
>>>Steffen Rheinhold said: > Hello, > > On Fri, 30 Oct 1998, G. Allen Morris III wrote: > > > Here is patch to solve one of you access problems. > > > > index: linux/fs/nfsd/auth.c > > [...] > > This worked! My AIX clients now gain correct group access rights again. > TNX! > > But there is still the "root trapping into directory" problem. I checked > with IRIX, AIX and Linux clients, all the same. For me this problem is > minor to the first one, but it should be fixed though, I think. > > When booting the linux server (RH5.1 based) I get some kernel messages, > which do not cause serious trouble, but maybe there is still something > running unstable. I think they started with 2.1.124: > > portmap: RPC call returned error 111 > RPC: task of released request still queued! > RPC: (task is on xprt_pending) > portmap: RPC call returned error 111 > RPC: task of released request still queued! > RPC: (task is on xprt_pending) > lockd_up: makesock failed, error=-111 > portmap: RPC call returned error 111 > RPC: task of released request still queued! > RPC: (task is on xprt_pending) > lockd_up: no pid, 2 users?? > portmap: RPC call returned error 111 > RPC: task of released request still queued! > RPC: (task is on xprt_pending) > > nfsd_init: initialized fhcache, entries=256 > lockd_up: no pid, 3 users?? > > The RPC: ones maybe are from the nfsclient, I mount some other share from > an Novell 4.1 server in NFS Mode. The lockd messages I don't know what > happens, but after reboot everything and all looks ok. I did not try yet > if lockd is server crash proof, is there any possibility to check this > (except of the "keep your claws off" button) ? > > > cu, Steffen > > srh@cc86.org > >
--------------------------------- G. Allen Morris III
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |