Your message dated Thu, 20 Oct 2005 02:48:45 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#332310: fixed in pgpool 2.6.3-2
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 5 Oct 2005 18:41:15 +0000
>From [EMAIL PROTECTED] Wed Oct 05 11:41:15 2005
Return-path: <[EMAIL PROTECTED]>
Received: from william.ironicdesign.com [216.180.99.12] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1ENECZ-0007Pa-00; Wed, 05 Oct 2005 11:41:15 -0700
Received: from hero.mallet-assembly.org (user-10lf9os.cable.mindspring.com 
[65.87.167.28])
        by william.ironicdesign.com (Postfix) with ESMTP id A419B460077;
        Wed,  5 Oct 2005 13:41:07 -0500 (CDT)
Received: by hero.mallet-assembly.org (sSMTP sendmail emulation); Wed,  5 Oct 
2005 14:41:11 -0400
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Michael Alan Dorman <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: pgpool: Invocation of killproc uses $NAME not $DAEMON
X-Mailer: reportbug 3.17
Date: Wed, 05 Oct 2005 14:41:11 -0400
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Package: pgpool
Severity: important
Tags: patch


The init.d script invokes killproc with $NAME as the parameter that
gets handed to start-stop-daemon's --exec flag (which is looked for in
/proc/pid/exe in order to identify the process to stop).

Unfortunately, the contents of /proc/pid/exe correspond to the full
path of the binary, so pgpool never matches, and the process isn't
found.  Changing the script to use $DAEMON instead of $NAME makes it
work again, and seems to remove the impetus for the following line (it
certainly works without it on my system, though I acknowledge that
there may be other issues I'm unaware of).

Anyway, a quick patch gets this working again.

--- pgpool.~1~  2005-09-05 04:31:14.000000000 -0500
+++ pgpool      2005-10-05 13:35:05.000000000 -0500
@@ -35,8 +35,8 @@
 
 
 d_stop() {
-       killproc -p $PIDFILE $NAME -INT
-       rm -f $PIDFILE          # see bug #321271
+       killproc -p $PIDFILE $DAEMON -INT
+#      rm -f $PIDFILE          # see bug #321271
 }
 
-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.13-t43p
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

---------------------------------------
Received: (at 332310-close) by bugs.debian.org; 20 Oct 2005 09:58:45 +0000
>From [EMAIL PROTECTED] Thu Oct 20 02:58:45 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
        id 1ESX2T-0005uP-00; Thu, 20 Oct 2005 02:48:45 -0700
From: Peter Eisentraut <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#332310: fixed in pgpool 2.6.3-2
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Thu, 20 Oct 2005 02:48:45 -0700
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Source: pgpool
Source-Version: 2.6.3-2

We believe that the bug you reported is fixed in the latest version of
pgpool, which is due to be installed in the Debian FTP archive:

pgpool_2.6.3-2.diff.gz
  to pool/main/p/pgpool/pgpool_2.6.3-2.diff.gz
pgpool_2.6.3-2.dsc
  to pool/main/p/pgpool/pgpool_2.6.3-2.dsc
pgpool_2.6.3-2_i386.deb
  to pool/main/p/pgpool/pgpool_2.6.3-2_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Peter Eisentraut <[EMAIL PROTECTED]> (supplier of updated pgpool package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Thu, 20 Oct 2005 10:45:45 +0200
Source: pgpool
Binary: pgpool
Architecture: source i386
Version: 2.6.3-2
Distribution: unstable
Urgency: low
Maintainer: Peter Eisentraut <[EMAIL PROTECTED]>
Changed-By: Peter Eisentraut <[EMAIL PROTECTED]>
Description: 
 pgpool     - connection pool server for PostgreSQL
Closes: 332310
Changes: 
 pgpool (2.6.3-2) unstable; urgency=low
 .
   * Use $DAEMON instead of $NAME for killproc and pidofproc (closes: #332310)
   * Changed log_begin_msg to log_daemon_msg
   * Added init script info block
Files: 
 ac4d32735891d2c4aeb66b2488070fb2 579 misc optional pgpool_2.6.3-2.dsc
 90120049540b94b19c440e97dff054da 5238 misc optional pgpool_2.6.3-2.diff.gz
 117e193d64bc5398311c0be092369392 70528 misc optional pgpool_2.6.3-2_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDV2OSTTx8oVVPtMYRAjOwAJ0aGlb3n6CFg0BwsldC+uNxNv0SnACglOtn
9zot0hN4NhpAU/4uY7HNTfA=
=KD8b
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to