Your message dated Wed, 14 Dec 2005 15:02:09 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#333590: fixed in shorewall 3.0.3-1
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; 12 Oct 2005 20:29:29 +0000
>From [EMAIL PROTECTED] Wed Oct 12 13:29:29 2005
Return-path: <[EMAIL PROTECTED]>
Received: from smtp4-g19.free.fr [212.27.42.30]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EPnE9-0006Ro-00; Wed, 12 Oct 2005 13:29:29 -0700
Received: from [127.0.0.1] (cac94-1-81-57-151-96.fbx.proxad.net [81.57.151.96])
by smtp4-g19.free.fr (Postfix) with ESMTP id 2AA253FD1F;
Wed, 12 Oct 2005 22:29:27 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: matthieu castet <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: /var/lib/shorewall/lock bug
X-Mailer: reportbug 3.17
Date: Wed, 12 Oct 2005 22:29:27 +0200
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: shorewall
Version: 2.4.5-1
Severity: important
Hi,
you should add some check on /var/lib/shorewall/lock in init.d script or
add information.
For an unknow reason (hard reset ?) /var/lib/shorewall/lock was still
here, and I didn't understand why shorewall seem to hang.
I reboot, it changes nothing, do a ctrl+c, the there was the same
problem on the next reboot.
yes I should have wait 60 s, but how could I know there was a timeout ?
Thanks
Matthieu
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.13
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Versions of packages shorewall depends on:
ii debconf [debconf-2.0] 1.4.58 Debian configuration management sy
ii iproute 20041019-3 Professional tools to control the
ii iptables 1.3.3-2 Linux kernel 2.4+ iptables adminis
Versions of packages shorewall recommends:
ii wget 1.10.1-2 retrieves files from the web
-- debconf information:
* shorewall/upgrade_20_22: true
shorewall/upgrade_14_20:
shorewall/upgrade_to_14:
shorewall/warnrfc1918:
shorewall/dont_restart:
shorewall/major_release:
---------------------------------------
Received: (at 333590-close) by bugs.debian.org; 14 Dec 2005 23:11:08 +0000
>From [EMAIL PROTECTED] Wed Dec 14 15:11:07 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 4.50)
id 1EmfdR-0004S1-1l; Wed, 14 Dec 2005 15:02:09 -0800
From: Lorenzo Martignoni <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.60 $
Subject: Bug#333590: fixed in shorewall 3.0.3-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Wed, 14 Dec 2005 15:02:09 -0800
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: shorewall
Source-Version: 3.0.3-1
We believe that the bug you reported is fixed in the latest version of
shorewall, which is due to be installed in the Debian FTP archive:
shorewall_3.0.3-1.diff.gz
to pool/main/s/shorewall/shorewall_3.0.3-1.diff.gz
shorewall_3.0.3-1.dsc
to pool/main/s/shorewall/shorewall_3.0.3-1.dsc
shorewall_3.0.3-1_all.deb
to pool/main/s/shorewall/shorewall_3.0.3-1_all.deb
shorewall_3.0.3.orig.tar.gz
to pool/main/s/shorewall/shorewall_3.0.3.orig.tar.gz
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.
Lorenzo Martignoni <[EMAIL PROTECTED]> (supplier of updated shorewall 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: Wed, 14 Dec 2005 23:36:35 +0100
Source: shorewall
Binary: shorewall
Architecture: source all
Version: 3.0.3-1
Distribution: unstable
Urgency: low
Maintainer: Lorenzo Martignoni <[EMAIL PROTECTED]>
Changed-By: Lorenzo Martignoni <[EMAIL PROTECTED]>
Description:
shorewall - Shoreline Firewall (Shorewall)
Closes: 333590 341942 342140
Changes:
shorewall (3.0.3-1) unstable; urgency=low
.
* New upstream release (Closes: #342140)
* Added Vietnamese debconf template (Closes: #341942)
* Patched the source in order to put the lockfile under /var/lock so
that it can be removed automatically during system startup (Closes:
#333590)
Files:
f291fae55abeae42f5a1c787f8a9611c 605 net optional shorewall_3.0.3-1.dsc
c77d8713f4ebf5fd0bbc05f1274487fc 187597 net optional
shorewall_3.0.3.orig.tar.gz
88824930942856f4bf98884f46d1b062 39839 net optional shorewall_3.0.3-1.diff.gz
d332e5053e750e4a91cdc3d15a572be2 214830 net optional shorewall_3.0.3-1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDoJ/mbFctcIsUOXURAnwNAKCUbseI7m4hi488xi2Ht127+jF8nwCgzvdD
8eFODpihyJmMoOF29ZKIYYA=
=hvpz
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
