Lines Matching +full:loss +full:- +full:of +full:- +full:lock
2 .\" The Regents of the University of California. All rights reserved.
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
10 .\" notice, this list of conditions and the following disclaimer in the
12 .\" 3. Neither the name of the University nor the names of its contributors
18 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
21 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
25 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
33 .Nd "apply or remove an advisory lock on an open file"
38 .Fd "#define LOCK_SH 0x01 /* shared file lock */"
39 .Fd "#define LOCK_EX 0x02 /* exclusive file lock */"
49 lock on the file associated with the file descriptor
51 A lock is applied by specifying an
53 argument that is one of
57 with the optional addition of
60 an existing lock
71 The locking mechanism allows two types of locks:
80 A shared lock may be
82 to an exclusive lock, and vice versa, simply by specifying
83 the appropriate lock type; this results in the previous
84 lock being released and the new lock applied (possibly
85 after other processes have gained and released the lock).
87 Requesting a lock on an object that is already locked
88 normally causes the caller to be blocked until the lock may be
105 do not result in multiple instances of a lock, but rather multiple
106 references to a single lock.
107 If a process holding a lock on a file
109 lose its lock.
119 However, only one of such interfaces should be used within
124 from the viewpoint of another process using
130 Processes blocked awaiting a lock may be awakened by signals.
132 .Rv -std flock
137 .Bl -tag -width Er
155 A lock was requested, but no locks are available.