1.\" $NetBSD: pidfile.3,v 1.7 2002/05/22 10:22:41 wiz Exp $ 2.\" 3.\" Copyright (c) 1999 The NetBSD Foundation, Inc. 4.\" All rights reserved. 5.\" 6.\" This code is derived from software contributed to The NetBSD Foundation 7.\" by Jason R. Thorpe. 8.\" 9.\" Redistribution and use in source and binary forms, with or without 10.\" modification, are permitted provided that the following conditions 11.\" are met: 12.\" 1. Redistributions of source code must retain the above copyright 13.\" notice, this list of conditions and the following disclaimer. 14.\" 2. Redistributions in binary form must reproduce the above copyright 15.\" notice, this list of conditions and the following disclaimer in the 16.\" documentation and/or other materials provided with the distribution. 17.\" 3. All advertising materials mentioning features or use of this software 18.\" must display the following acknowledgement: 19.\" This product includes software developed by the NetBSD 20.\" Foundation, Inc. and its contributors. 21.\" 4. Neither the name of The NetBSD Foundation nor the names of its 22.\" contributors may be used to endorse or promote products derived 23.\" from this software without specific prior written permission. 24.\" 25.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS 26.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED 27.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 28.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS 29.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR 30.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 31.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 32.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN 33.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 34.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 35.\" POSSIBILITY OF SUCH DAMAGE. 36.\" 37.Dd June 5, 1999 38.Dt PIDFILE 3 39.Os 40.Sh NAME 41.Nm pidfile 42.Nd write a daemon pid file 43.Sh LIBRARY 44.Lb libutil 45.Sh SYNOPSIS 46.Fd #include \*[Lt]util.h\*[Gt] 47.Ft int 48.Fn pidfile "const char *basename" 49.Sh DESCRIPTION 50.Fn pidfile 51writes a file containing the process ID of the program to the 52.Pa /var/run 53directory. The file name has the form 54.Pa /var/run/basename.pid . 55If the 56.Ar basename 57argument is NULL, 58.Nm 59will determine the program name and use that instead. 60.Pp 61The pid file can be used as a quick reference if 62the process needs to be sent a signal. When the program exits, 63the pid file will be removed automatically, unless the program 64receives a fatal signal. 65.Pp 66Note that only the first invocation of 67.Nm 68causes a pid file to be written; subsequent invocations have no effect 69unless a new 70.Ar basename 71is supplied. 72If called with a new 73.Ar basename , 74.Fn pidfile 75will remove the old pid file and write the new one. 76.Sh RETURN VALUES 77.Fn pidfile 78returns 0 on success and -1 on failure. 79.Sh SEE ALSO 80.Xr atexit 3 81.Sh HISTORY 82The 83.Nm 84function call appeared in 85.Nx 1.5 . 86.Sh BUGS 87.Fn pidfile 88uses 89.Xr atexit 3 90to ensure the pidfile is unlinked at program exit. 91However, programs that use the 92.Xr _exit 2 93function (for example, in signal handlers) 94will not trigger this behaviour. 95