|File: [cvs.NetBSD.org] / src / lib / libutil / pidlock.3 (download)
Revision 1.3, Mon Jun 8 10:58:45 1998 UTC (22 years, 2 months ago) by lukem
CVS Tags: wrstuden-devbsize-base, wrstuden-devbsize-19991221, wrstuden-devbsize, netbsd-1-5-base, netbsd-1-5-RELEASE, netbsd-1-5-PATCH003, netbsd-1-5-PATCH002, netbsd-1-5-PATCH001, netbsd-1-5-BETA2, netbsd-1-5-BETA, netbsd-1-5-ALPHA2, netbsd-1-5, netbsd-1-4-base, netbsd-1-4-RELEASE, netbsd-1-4-PATCH003, netbsd-1-4-PATCH002, netbsd-1-4-PATCH001, netbsd-1-4, minoura-xpg4dl-base, minoura-xpg4dl, comdex-fall-1999-base, comdex-fall-1999
Changes since 1.2: +1 -2
don't need trailing empty paragraph
.\" $NetBSD: pidlock.3,v 1.3 1998/06/08 10:58:45 lukem Exp $
.\" Copyright 1996, 1997 by Curt Sampson <firstname.lastname@example.org>
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS
.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
.\" POSSIBILITY OF SUCH DAMAGE.
.Dd November 10, 1996
.Dt PIDLOCK 3
.Nm pidlock ,
.Nm ttylock ,
.Nd locks based on files containing PIDs
.Fd #include <util.h>
.Fn pidlock "const char *lockfile" "int flags" "pid_t *locker" "const char *info"
.Fn ttylock "const char *tty" "int flags" "pid_t *locker"
.Fn ttyunlock "const char *tty"
.Fn ttylock ,
functions attempt to create a lockfile for an arbitrary resource that
only one program may hold at a time. (In the case of
.Fn ttylock ,
this is access to a tty device.) If the
function succeeds in creating the lockfile, it will succeed for
no other program calling it with the same lockfile until the original
calling program has removed the lockfile or exited. The
function will remove the lockfile created by
.Fn ttylock .
These functions use the method of creating a lockfile traditionally
used by UUCP software. This is described as follows in the
documentation for Taylor UUCP:
.Bd -filled -offset indent
The lock file normally contains the process ID of the locking
process. This makes it easy to determine whether a lock is still
valid. The algorithm is to create a temporary file and then link
it to the name that must be locked. If the link fails because a
file with that name already exists, the existing file is read to
get the process ID. If the process still exists, the lock attempt
fails. Otherwise the lock file is deleted and the locking algorithm
The PID is stored in ASCII format, with leading spaces to pad it
out to ten characters, and a terminating newline. This
implementation has been extended to put the hostname
on the second line of the file, terminated with a newline, and
optionally an arbitrary comment on the third line of the file, also
terminated with a newline. If a comment is given, but
is not, a blank line will be written as the second line of the file.
function will attempt to create the file
and put the current process's pid in it. The
function will do the same, but should be passed only the base name
(with no leading directory prefix) of the tty to be locked; it will
test that the tty exists in
and is a character device, and then create
the file in the
directory and prefix the filename with
.Pa LCK.. .
function to remove this lock.
The following flags may be passed in
.Pa flags :
.Bl -tag -width Dv -offset indent
.It Dv PIDLOCK_NONBLOCK
The function should return immediately when a lock is held by another
active process. Otherwise the function will wait (forever, if necessary)
for the lock to be freed.
.It Dv PIDLOCK_USEHOSTNAME
The hostname should be compared against the hostname in the second
line of the file (if present), and if they differ, no attempt at
checking for a living process holding the lock will be made, and
the lockfile will never be deleted. (The process is assumed to be
alive.) This is used for locking on NFS or other remote filesystems.
(The function will never create a lock if
is specified and no hostname is present.)
is non-null, it will contain the PID of the locking process, if there
is one, on return.
is non-null and the lock succeeds, the string it points to will be
written as the third line of the lock file.
.Sh RETURN VALUES
Zero is returned if the operation was successful; on an error a -1
is returned and a standard error code is left in the global location errno.
These are among the values left in
returns a failure:
.Bl -tag -width Er
.It Bq Er EPERM
The current process does not have some of the privileges necessary
to perform the lock. These include read and write access to the lock
directory, and read access to the current lockfile, if it exists.
.It Bq Er ENOENT
A component of a specified pathname did not exist, or the pathname
was an empty string.
.It Bq Er EWOULBLOCK
Another runnning process has a lock and the
flag was specified.
.It Bq Er ENAMETOOLONG
A component of the path name exceeded 255 (MAXNAMELEN) characters,
or an entire path name exceeded 1023 (MAXPATHLEN-1) characters.
.\" .Sh SEE ALSO
functions appeared in
.Nx 1.3 .
Curt Sampson <email@example.com>
The lockfile format breaks if a pid is longer than ten digits when
printed in decimal form.
The PID returned will be the pid of the locker on the remote machine if
is specified, but there is no indication that this is not on the local