Debian Policy (9.1.4) states that /run is cleared on boot, so packages must not assume that any files or directories under /run exist unless the package has arranged to create those files or directories since the last reboot. Even more so, pgpool2's default configuration sets it's socket file to exist under /var/run/postgresql.
pgpool2's init script does not set up this directory, so even if one were to create it manually, the problem persists after a reboot. When pgpool2 coexists with PostgreSQL, the latter makes sure that directory exists, so the problem doesn't show. But it will happen when using pgpool2 by itself in a machine without PostgreSQL. Since it is a violation of Debian Policy and makes the package unusable when installed by itself, I believe the severity of this bug should be increased to 'serious' -- Prof. Ernesto Hernández-Novich - MYS-220C - @iamemhn Geek by nature, Linux by choice, Debian of course. If you can't aptitude it, it isn't useful or doesn't exist. GPG Key Fingerprint = 438C 49A2 A8C7 E7D7 1500 C507 96D6 A3D6 2F4C 85E3 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
