Hi,

the current version of Pound uses a fixed location and name for pidfiles
(/var/run/pound.pid.<pid>)
The watchdog we use on our site depends on the pids in the pidfiles to
find out whether one or more instances of Pound are down. Since the
pidfiles all have the same basic name, the watchdog can not distinguish
which Pound instance to restart and often restart the wrong one.

To get around this problem, I added a commandline option -p to specify
the prefix for the pidfile names. For example:

pound -p /var/run/pound-instance-5.pid

will create a pidfile /var/run/pound-instance-5.pid.<pid>

Aside from this commandline option, I also rewrote the commandline
arguments parsing. It now uses getopt_long instead of multiple strcmp().

The patch can be downloaded here:
http://deepstar.ekonomika.be/Projects/patches/pound-1.8.3-pidfile.patch.gz

greets,[...]

On Mon, May 02, 2005 at 05:52:25PM +0200, Steven Van Acker wrote:[...]

Hi,

I made mistake to believe that the pid number in the pidfile name is
really needed. This is of course only needed when there are several
instanced of pound running, all using the same pidfile name (like is the
case with the unpatched version of Pound)

I've changed the patch to not include the pid number in the pidfile
name. To be backwards compatible, I add the pidnumber if a pidfile is
not supplied on the commandline.

I also changed "pidfileprefix" to just "pidfile", since its no longer a
prefix.

The new patch can be found here :
http://deepstar.ekonomika.be/Projects/patches/pound-1.8.3-pidfile-2.patch.gz

greets,[...]