Lines Matching full:with
20 the kernel has decided to proceed with a read, but before the
46 with a "mandatory" locking scheme, whereby the operating system kernel would
78 to run mandatory lock candidates with setgid privileges.
83 I have considered the implementations of mandatory locking available with
91 contravention of SVID 3, which states that only calls to open() with the
93 definition, which is the "Right Thing", since only calls with O_TRUNC can
96 HP-UX even disallows open() with O_TRUNC for a file with advisory locks, not
122 2. If a process has locked a region of a file with a mandatory read lock, then
125 released, unless the process has opened the file with the O_NONBLOCK
126 flag in which case the system call will return immediately with the error
129 3. If a process has locked a region of a file with a mandatory write lock, all
131 unless a process has opened the file with the O_NONBLOCK flag in which case
132 the system call will return immediately with the error status EAGAIN.
134 4. Calls to open() with O_TRUNC, or to creat(), on a existing file that has
135 any mandatory locks owned by other processes will be rejected with the
139 shared (via mmap() with MAP_SHARED) will be rejected with the error status
142 6. Attempts to create a shared memory map of a file (via mmap() with MAP_SHARED)
143 that has any mandatory locks in effect will be rejected with the error status
175 administratively enabled by mounting with "-o mand". That mount option
180 with this disabled will reject attempts to mount filesystems with the
181 "mand" mount option with the error status EPERM.