Browse Source

multiple calls to pidfile(3) are actually ok, but there are problems if you change the basename

OPENBSD_3_0
jakob 23 years ago
parent
commit
665a8f810d
1 changed files with 7 additions and 5 deletions
  1. +7
    -5
      src/lib/libutil/pidfile.3

+ 7
- 5
src/lib/libutil/pidfile.3 View File

@ -1,4 +1,4 @@
.\" $OpenBSD: pidfile.3,v 1.1 2001/09/28 20:16:42 jakob Exp $
.\" $OpenBSD: pidfile.3,v 1.2 2001/09/28 20:27:56 jakob Exp $
.\" $NetBSD: pidfile.3,v 1.2 2001/04/12 22:34:31 sommerfeld Exp $ .\" $NetBSD: pidfile.3,v 1.2 2001/04/12 22:34:31 sommerfeld Exp $
.\" .\"
.\" Copyright (c) 1999 The NetBSD Foundation, Inc. .\" Copyright (c) 1999 The NetBSD Foundation, Inc.
@ -61,10 +61,6 @@ The pid file can be used as a quick reference if
the process needs to be sent a signal. When the program exits, the process needs to be sent a signal. When the program exits,
the pid file will be removed automatically, unless the program the pid file will be removed automatically, unless the program
receives a fatal signal. receives a fatal signal.
.Pp
Note that only the first invocation of
.Nm
causes a pid file to be written; subsequent invocations have no effect.
.Sh RETURN VALUES .Sh RETURN VALUES
.Fn pidfile .Fn pidfile
returns 0 on success and -1 on failure. returns 0 on success and -1 on failure.
@ -75,3 +71,9 @@ The
.Nm .Nm
function call appeared in function call appeared in
.Ox 3.0 . .Ox 3.0 .
.Sh CAVEATS
If
.Fn pidfile
is called multiple times with different
.Ar basename ,
only the last pidfile will be removed upon exit.

Loading…
Cancel
Save