Lines Matching refs:mandatory

8 1. What is  mandatory locking?
27 with a "mandatory" locking scheme, whereby the operating system kernel would
32 The System V mandatory locking scheme was intended to have as little impact as
34 as candidates for mandatory locking, and using the existing fcntl()/lockf()
40 to entire files, so the mandatory locking rules also have byte level
43 Note 2: POSIX.1 does not specify any scheme for mandatory locking, despite
44 borrowing the fcntl() locking scheme from System V. The mandatory locking
47 2. Marking a file for mandatory locking
50 A file is marked as a candidate for mandatory locking by setting the group-id
57 modified to recognize the special case of a mandatory lock candidate and to
59 to run mandatory lock candidates with setgid privileges.
64 I have considered the implementations of mandatory locking available with
71 another process has outstanding mandatory locks. This is in direct
78 just mandatory locks. That would appear to contravene POSIX.1.
81 prevent mandatory locks from being applied to an mmap()'ed file, but  HP-UX
86 only from mandatory locks - that is what is currently implemented.
89 mandatory locks, so reads and writes to locked files always block when they
101    locks using flock() never result in a mandatory lock.
103 2. If a process has locked a region of a file with a mandatory read lock, then
110 3. If a process has locked a region of a file with a mandatory write lock, all
116    any mandatory locks owned by other processes will be rejected with the
119 5. Attempts to apply a mandatory lock to a file that is memory mapped and
124    that has any mandatory locks in effect will be rejected with the error status
133 for the purposes of mandatory locking.
141 Note 3: I may have overlooked some system calls that need mandatory lock
148 Not even root can override a mandatory lock, so runaway processes can wreak