Bug 4707

We recently installed a new file server on our network,
running a fresh RH 6.0 install on a raid filesystem. We used
the release 2.2.5 SMP kernel and the released knfsd to set
up an NFS exported partition, and noticed problems deleting
the ~/.gnome and ~/.enlightenment directories of an NFS
client.

gnome and enlightenment appear to install these directories
with the following permissions:

drwx--S---

From the client:rm -rf ~/.enlightenment would fail to delete
the directory (which is nfs mounted from the NFS server
running RH6, described above). However, if we used chmod g-s
~/.enlightenment from the client, we could delete the
directory.

To be sure that we wer seeing someting reproducible, from
the client we did 'mkdir ~/foo; chmod 700 ~/foo; chmod g+s
~/foo; rm -rf ~/foo' and got the same problem.

Finally, we noticed some other strangeness, like if we
created a directory with these weird permissions, and used
'touch ~/foo/foobar' to create an empty file, 'ls ~/foo'
would NOT list foobar! Stranger still, 'rm ~/foo/foobar'
would then delete foobar, even though ls didn't see it.

We then duplicated the test on a FreeBSD NFS server running
on the network, and saw no problems. We may yet try the user
space NFS server.

As an aside, the other thing about KNFSD that really bothers
us is that file handles aren't preserved when the server
reboots. I recall from an earlier stint with user space nfsd
that it could handle this. It would be nice to have RPMS
available for user space NFS with the Red Hat distribution.


------- Additional Comments From   08/26/99 01:28 -------
this looks like mandatory locking stuff.
/usr/src/linux/Documentation/mandatory.txt

It is not setgid if group has no execute permissions but
file (directory in this case) is marked to have mandatory locks
applied.