FLOCK(2) BSD System Calls Manual FLOCK(2)

NAME
     fflloocckk - apply or remove an advisory lock on an open file

SYNOPSIS
     ##iinncclluuddee <>
     ##ddeeffiinnee   LLOOCCKKSSHH   11    //** sshhaarreedd lloocckk **//
     ##ddeeffiinnee   LLOOCCKKEEXX   22    //** eexxcclluussiivvee lloocckk **//
     ##ddeeffiinnee   LLOOCCKKNNBB   44    //** ddoonn''tt bblloocckk wwhheenn lloocckkiinngg **//
     ##ddeeffiinnee   LLOOCCKKUUNN   88    //** uunnlloocckk **//

     int
     fflloocckk(int fd, int operation);

DESCRIPTION
     FFlloocckk() applies or removes an advisory lock on the file associated with
     the file descriptor fd.  A lock is applied by specifying an operation
     parameter that is one of LOCKSH or LOCKEX with the optional addition of
     LOCKNB.  To unlock an existing lock operation should be LOCKUN.

     Advisory locks allow cooperating processes to perform consistent opera-
     tions on files, but do not guarantee consistency (i.e., processes may
     still access files without using advisory locks possibly resulting in
     inconsistencies).

     The locking mechanism allows two types of locks: shared locks and
     exclusive locks.  At any time multiple shared locks may be applied to a
     file, but at no time are multiple exclusive, or both shared and exclu-
     sive, locks allowed simultaneously on a file.

     A shared lock may be upgraded to an exclusive lock, and vice versa, sim-
     ply by specifying the appropriate lock type; this results in the previous
     lock being released and the new lock applied (possibly after other pro-
     cesses have gained and released the lock).

     Requesting a lock on an object that is already locked normally causes the
     caller to be blocked until the lock may be acquired.  If LOCKNB is
     included in operation, then this will not happen; instead the call will
     fail and the error EWOULDBLOCK will be returned.

NNOOTTEESS
     Locks are on files, not file descriptors.  That is, file descriptors
     duplicated through dup(2) or fork(2) do not result in multiple instances
     of a lock, but rather multiple references to a single lock.  If a process
     holding a lock on a file forks and the child explicitly unlocks the file,
     the parent will lose its lock.

     Processes blocked awaiting a lock may be awakened by signals.

RETURN VALUES
     Zero is returned if the operation was successful; on an error a -1 is
     returned and an error code is left in the global location errno.

EERRRROORRSS
     The fflloocckk() call fails if:

     [EWOULDBLOCK]      The file is locked and the LOCKNB option was speci-
                        fied.

     [EBADF]            The argument fd is an invalid descriptor.

     [EINVAL]           The argument fd refers to an object other than a file.

     [ENOTSUP]          The referenced descriptor is not of the correct type.

SEE ALSO
     close(2), dup(2), execve(2), fork(2), open(2)

HISTORY     The fflloocckk() function call appeared in 4.2BSD.

4.2 Berkeley Distribution      December 11, 1993     4.2 Berkeley Distribution