Huh? That means (the admittedly rather useless, but still common)
setgid directories without group write are inacessible. They get
created that way in a setgid directory if you umask group execute.
FWIW, Solaris lets you access "mandantory locked" directories, but
not files.
> > nfs server always clears the setgid bit of a file when it is written
> > to (this should not occur if the file is marked for mandatory locking).
>
> The server drops handles when it needs to. That means mandatory locks
> won't work. Mandatory locks aren't defined over NFS either.
Right. And if you don't allow access to mandantory locked files, there
is no problem here.
> > Also, in playing around with the locking I noted that locks on the
> > server are independent from locks on the clients. That is, if one
> > NFS client locks a file, the lock is seen by other NFS clients.
>
> Make sure you have an rpc.lockd running
It is, and statd.
/Anders
-
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/