Lines Matching refs:locks

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