3 ms·
Not quite answering your question, but the man page says Conflicting lock combinations (i.e., a read lock and a write lock or two write locks) where one lock
by dooglius 3y ago
Not quite answering your question, but the man page says
Conflicting lock combinations (i.e., a read lock and a write lock or two write locks) where one lock is an open file description lock and the other is a traditional record lock conflict even when they are acquired by the same process on the same file descriptor.
- wahern 3y agoI think that answers it. And looking back at the specification in the SUSv5 draft, it seems this and analogous behavior has been codified--an OFD lock conflicts with a process-private lock and vice-versa. So there's only one reasonable option for mapping OFD locks to NFS locks, which is that they both map to the same NFS server lock in the same manner (unlike BSD flock, both support record locking).