Package: pgpool2
Version: 3.1.3-4
Severity: important
Dear Maintainer,
* What led up to the situation?
Trying to install pgpool2 on a machine to act as a frontend
for several backend PostgreSQL databases. The machine *does not*
and *must not* have PostgreSQL installed, so there was no
postgresql-9.1 package there.
* What exactly did you do (or not do) that was effective (or
ineffective)?
aptitude install pgpool2
* What was the outcome of this action?
The pgpool2 service would not start because the PID-file
defined in the init script has /var/run/postgresql/pgpool.pid
and /var/run/postgresql does not exist, given that there's
no PostgreSQL installed there.
* What outcome did you expect instead?
pgpool must be able to run on machines that don't have PostgreSQL
installed, so assuming /var/run/postgresql exists is not right.
Since pgpool could be run on its own, its PID file shouldn't be
related to any other package being installed.
I expected the init script to use /var/run/pgpool.pid.
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages pgpool2 depends on:
ii libc6 2.13-38
ii libpgpool0 3.1.3-4
ii libpq5 9.1.8-1
ii lsb-base 4.1+Debian8
ii postgresql-common 134wheezy3
ii ucf 3.0025+nmu3
pgpool2 recommends no packages.
pgpool2 suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
