Your message dated Sat, 20 Aug 2005 17:32:04 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#324017: fixed in cron 3.0pl1-90
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; 19 Aug 2005 19:46:48 +0000
>From [EMAIL PROTECTED] Fri Aug 19 12:46:47 2005
Return-path: <[EMAIL PROTECTED]>
Received: from pool-70-107-45-7.ny325.east.verizon.net (localhost.localdomain) 
[70.107.45.7] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1E6Cov-0005Jm-00; Fri, 19 Aug 2005 12:46:29 -0700
Received: from rick by localhost.localdomain with local (Exim 4.52)
        id 1E6CoQ-0007ts-R8; Fri, 19 Aug 2005 15:45:58 -0400
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Rick Friedman <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: Cron daemon dies when a cronjob is about to start
X-Mailer: reportbug 3.15
Date: Fri, 19 Aug 2005 15:45:58 -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: cron
Version: 3.0pl1-88
Severity: grave
Justification: renders package unusable


The cron daemon runs as normal until a cronjob starts up. Actually, I
don't even know if the cronjob actually starts. What I DO know is that
at the start time of any cronjob, the cron daemon process mysteriously
dies. No messages in any logs. Before a cronjob starts, the cron daemon
process is running. After the (supposed) start of a cronjob, the cron
daemon process is gone.

Downgrading to version 3.0pl1-87 resolves the problem.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-k7
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages cron depends on:
ii  adduser                       3.67       Add and remove users and groups
ii  debianutils                   2.14.2     Miscellaneous utilities specific t
ii  libc6                         2.3.5-3    GNU C Library: Shared libraries an
ii  libpam0g                      0.76-23    Pluggable Authentication Modules l
ii  libselinux1                   1.24-4     SELinux shared libraries

Versions of packages cron recommends:
ii  exim4                         4.52-1     metapackage to ease exim MTA (v4) 
ii  exim4-daemon-light [mail-tran 4.52-1     lightweight exim MTA (v4) daemon

-- no debconf information

---------------------------------------
Received: (at 324017-close) by bugs.debian.org; 21 Aug 2005 00:41:45 +0000
>From [EMAIL PROTECTED] Sat Aug 20 17:41:45 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
        id 1E6dkq-0002vl-00; Sat, 20 Aug 2005 17:32:04 -0700
From: Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#324017: fixed in cron 3.0pl1-90
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Sat, 20 Aug 2005 17:32:04 -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: cron
Source-Version: 3.0pl1-90

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

cron_3.0pl1-90.diff.gz
  to pool/main/c/cron/cron_3.0pl1-90.diff.gz
cron_3.0pl1-90.dsc
  to pool/main/c/cron/cron_3.0pl1-90.dsc
cron_3.0pl1-90_i386.deb
  to pool/main/c/cron/cron_3.0pl1-90_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.
Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]> (supplier of updated cron 
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: Sun, 21 Aug 2005 02:25:10 +0200
Source: cron
Binary: cron
Architecture: source i386
Version: 3.0pl1-90
Distribution: unstable
Urgency: low
Maintainer: Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]>
Changed-By: Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]>
Description: 
 cron       - management of regular background processing
Closes: 324017
Changes: 
 cron (3.0pl1-90) unstable; urgency=low
 .
   * Fix SIGSEV due to a NULL free in the libselinux code, as a consequence
     cron dies before cronjobs are started (Closes: #324017)
Files: 
 11ef6bc7503b9ca65cae5f9a902a774b 770 admin important cron_3.0pl1-90.dsc
 f22f41b702c2627bf4cd971df28b1f7d 48570 admin important cron_3.0pl1-90.diff.gz
 e88e729fae585e5484148edea3aaa20e 59878 admin important cron_3.0pl1-90_i386.deb

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

iQCVAwUBQwfKIPtEPvakNq0lAQLjZQP/QIZG4gtmuNng3gWVDKfbEt4SQMAFxb4S
Bz2iOLgBP/4PgfVF99KHY07yBGl/VkljDmX6GWKCDPvL1XpJDjJltPXGJou/Lsnc
VTNy9EIYd2jrBuJ++ugYNbtJ6CRBoj95YW20OruVXd7xYNP2Yeg4d6kMgfnmtqvi
8bcanEclpz8=
=UTjO
-----END PGP SIGNATURE-----


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

Reply via email to