Your message dated Thu, 29 Jun 2006 01:48:09 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#369840: fixed in runit 1.6.0-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)

--- Begin Message ---
Package: runit
Version: 1.4.1-1
Severity: normal

Hi,

I just noticed that some of my log directories had many more log files in
them than the value of the 'n' parameter in the corresponding svlogd config.

A great deal of these were unprocessed .u files. Unfortunately, I'm not sure
if there were also more .s files than configured, but I set up an experiment
if you like.

If the behaviour of not deleting .u files during log rotation is
intentional, svlogd(8) should probably point it out. It currently does not.
I expected .u and .s files to be treated the same way for the purposes of
log rotation (as is the case with multilog).

Andras

-- System Information:
Debian Release: unstable
  APT prefers dapper-updates
  APT policy: (1200, 'dapper-updates'), (1200, 'dapper-security'), (1200, 
'dapper'), (1200, 'breezy-security'), (1200, 'breezy'), (100, 'experimental'), 
(100, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16.10+skasv3pre9-chardonnay-skas3-v9-pre9
Locale: LANG=C, LC_CTYPE=hu_HU (charmap=ISO-8859-2)

-- no debconf information

-- 
                 Andras Korn <korn at chardonnay.math.bme.hu>
                 <http://chardonnay.math.bme.hu/~korn/> QOTD:
                  Oops. My brain just hit another bad sector.


--- End Message ---
--- Begin Message ---
Source: runit
Source-Version: 1.6.0-1

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

runit_1.6.0-1.diff.gz
  to pool/main/r/runit/runit_1.6.0-1.diff.gz
runit_1.6.0-1.dsc
  to pool/main/r/runit/runit_1.6.0-1.dsc
runit_1.6.0-1_powerpc.deb
  to pool/main/r/runit/runit_1.6.0-1_powerpc.deb
runit_1.6.0.orig.tar.gz
  to pool/main/r/runit/runit_1.6.0.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.
Gerrit Pape <[EMAIL PROTECTED]> (supplier of updated runit 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, 29 Jun 2006 07:55:14 +0000
Source: runit
Binary: runit
Architecture: source powerpc
Version: 1.6.0-1
Distribution: unstable
Urgency: low
Maintainer: Gerrit Pape <[EMAIL PROTECTED]>
Changed-By: Gerrit Pape <[EMAIL PROTECTED]>
Description: 
 runit      - a UNIX init scheme with service supervision
Closes: 369840
Changes: 
 runit (1.6.0-1) unstable; urgency=low
 .
   * new upstream version.
     * cleanup *.t files possibly leftover by processor when interrupted by
       signal, also on startup (thx Andras Korn, closes: #369840).
Files: 
 ab7acd6e791dc1d076c32486dc5b04a1 626 admin optional runit_1.6.0-1.dsc
 e7b9fbc0fa8843662df3bb8b7e68b505 100728 admin optional runit_1.6.0.orig.tar.gz
 25529b408257b3592ecde7e995f4fddb 8781 admin optional runit_1.6.0-1.diff.gz
 ab3d893cc5e29ee06e7f56e399863fbf 105302 admin optional 
runit_1.6.0-1_powerpc.deb

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

iD8DBQFEo4iiGJoyQbxwpv8RAkGYAJ9ylDjqKhiBPr49rNth9QaKZArDPQCgjMAK
LO44T9PjiIKBrTApBiTGMa0=
=kRY4
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to