Date: Thu, 13 Nov 2003 12:04:34 +0100 From: Joan Picanyol <lists-freebsd-hackers@biaix.org> To: freebsd-hackers@freebsd.org Subject: Re: non-root process and PID files Message-ID: <20031113110434.GA51335@grummit.biaix.org> In-Reply-To: <3FB360BE.779DB42F@mindspring.com> References: <3F9CF3F6.8307.ABC1250@localhost> <20031111071944.GA5778@lizzy.catnook.com> <3FB360BE.779DB42F@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* Terry Lambert <tlambert2@mindspring.com> [20031113 11:46]: > Jos Backus wrote: > > On Mon, Oct 27, 2003 at 10:31:18AM -0500, Dan Langille wrote: > > > 1 - write your PID immediately, and the file is chown root:wheel > > > 2 - write your PID to /var/run/myapp/myapp.pid where /var/run/myapp/ > > > is chown myapp:myapp > > > > > > Of the two, I think #1 is cleaner as it does not require another > > > directory with special permissions. > > > > > > Any suggestions? > > > > Why use pid files at all if you could be using a process supervisor instead? > > Who supervises the supervisor? Sure, you can take the English > Bobby approach (init dies, the kernel yells "Help me, human, or > I shall yell 'Help me Human!' again", and tries to start software > that will never start over and over), but that solves nothing; Let the supervisor be process 1: http://multivac.cwru.edu/svscan-1/ http://smarden.org/runit/ http://www.fefe.de/minit/ qvb -- pica
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031113110434.GA51335>