Lines Matching refs:locks

37 processes. File locks are applied using the flock() and fcntl() system calls
39 normally a process' responsibility to check for locks on a file it wishes to
59 interface for applying locks just as if they were normal, advisory locks.
97 another process has outstanding mandatory locks. This is in direct
103 HP-UX even disallows open() with O_TRUNC for a file with advisory locks, not
104 just mandatory locks. That would appear to contravene POSIX.1.
107 prevent mandatory locks from being applied to an mmap()'ed file, but  HP-UX
108 also disallows advisory locks for such a file. SVID actually specifies the
112 only from mandatory locks - that is what is currently implemented.
115 mandatory locks, so reads and writes to locked files always block when they
125 1. Mandatory locks can only be applied via the fcntl()/lockf() locking
127    locks using flock() never result in a mandatory lock.
142    any mandatory locks owned by other processes will be rejected with the
150    that has any mandatory locks in effect will be rejected with the error status