Ok
> Then, I was also told that files marked for mandatory locking were
> not openable via NFS (even if they weren't regular files). The first
This is correct
> fix was pretty obvious, make sure the file is a regular file before
> deciding it is marked for mandatory locking. I also noted that the
That isnt a fix
> 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.
> 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
-
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/