Your message dated Mon, 3 Oct 2005 03:49:27 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#331299: exim4: bashisms in init script
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; 2 Oct 2005 21:31:21 +0000
>From [EMAIL PROTECTED] Sun Oct 02 14:31:21 2005
Return-path: <[EMAIL PROTECTED]>
Received: from ms-smtp-02.nyroc.rr.com [24.24.2.56]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EMBQW-00041U-00; Sun, 02 Oct 2005 14:31:21 -0700
Received: from andromeda (cpe-69-202-136-66.twcny.res.rr.com [69.202.136.66])
by ms-smtp-02.nyroc.rr.com (8.12.10/8.12.10) with ESMTP id
j92LVIDK024968
for <[EMAIL PROTECTED]>; Sun, 2 Oct 2005 17:31:18 -0400 (EDT)
Received: from pryzbyj by andromeda with local (Exim 4.52)
id 1EMBQT-0001Jc-Me
for [EMAIL PROTECTED]; Sun, 02 Oct 2005 17:31:17 -0400
Date: Sun, 2 Oct 2005 17:31:17 -0400
To: Debian BTS Submission <[EMAIL PROTECTED]>
Subject: exim4: bashisms in init script
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.9i
From: Justin Pryzby <[EMAIL PROTECTED]>
X-Virus-Scanned: Symantec AntiVirus Scan Engine
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: exim4
Severity: normal
Version: 4.52-1
File: /etc/init.d/exim4
The exim4 initscript /etc/init.d/exim4 uses:
#!/bin/sh
and
kill_all_exims()
{
SIG="${1:-TERM}"
for pid in $(pidof $NAME); do
if [ "$(readlink /proc/$pid/root)" == "/" ]; then
kill -$SIG $pid
fi
done
}
Isn't '$(' a bashism (That's what the vim maintainer said in #319825)
---------------------------------------
Received: (at 331299-done) by bugs.debian.org; 3 Oct 2005 08:44:06 +0000
>From [EMAIL PROTECTED] Mon Oct 03 01:44:06 2005
Return-path: <[EMAIL PROTECTED]>
Received: from ms-smtp-03.nyroc.rr.com [24.24.2.57]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EMLva-0003Sw-00; Mon, 03 Oct 2005 01:44:06 -0700
Received: from andromeda (cpe-69-202-136-66.twcny.res.rr.com [69.202.136.66])
by ms-smtp-03.nyroc.rr.com (8.12.10/8.12.10) with ESMTP id
j938i17Z018852
for <[EMAIL PROTECTED]>; Mon, 3 Oct 2005 04:44:03 -0400 (EDT)
Received: from pryzbyj by andromeda with local (Exim 4.52)
id 1EML4h-0001j9-KP
for [EMAIL PROTECTED]; Mon, 03 Oct 2005 03:49:27 -0400
Date: Mon, 3 Oct 2005 03:49:27 -0400
To: [EMAIL PROTECTED]
Subject: Re: Bug#331299: exim4: bashisms in init script
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.9i
From: Justin Pryzby <[EMAIL PROTECTED]>
X-Virus-Scanned: Symantec AntiVirus Scan Engine
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
On Mon, Oct 03, 2005 at 09:47:15AM +0200, Marc Haber wrote:
> On Sun, Oct 02, 2005 at 11:40:29PM +0100, Adam D. Barratt wrote:
> > The ==, otoh, *is* non-compliant and a Bashism.
>
> Thanks for spotting this, fixed in svn.
Heh. The philosophers are always talking about conditions of
discovery vs conditions of justification, or something..
Bug closed, I guess.
--
Clear skies,
Justin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
