Your message dated Thu, 30 Mar 2006 11:02:09 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#356002: fixed in syslog-ng 1.9.9-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)

--- Begin Message ---
Package: syslog-ng
Version: 1.9.9-1
Severity: normal

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

I removed syslog-ng 1.9.9-1 because of the log statistics that keep getting 
dumped to the syslog, which keep showing up in logcheck, which I have not had 
success 
ignoring.  I removed syslog-ng and replaced it with sysklogd, but then I 
noticed the log statistics were still showing up in logcheck.  Then I saw that 
syslog-ng was still 
running.  So I purged syslog-ng, but syslog-ng was still running.  So I killed 
syslog-ng and removed /var/run/syslog-ng.pid.

Removing and/or purging it should stop the daemon, shouldn't it?

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

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

iD8DBQFED9iv5+GdyTDsrJsRAq10AKCifEK5Uh61xV7PVvcBuFJIPC55GACgipBG
RyNk4550p0L/TAKhsXgRWBA=
=wnlE
-----END PGP SIGNATURE-----


--- End Message ---
--- Begin Message ---
Source: syslog-ng
Source-Version: 1.9.9-2

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

syslog-ng_1.9.9-2.diff.gz
  to pool/main/s/syslog-ng/syslog-ng_1.9.9-2.diff.gz
syslog-ng_1.9.9-2.dsc
  to pool/main/s/syslog-ng/syslog-ng_1.9.9-2.dsc
syslog-ng_1.9.9-2_i386.deb
  to pool/main/s/syslog-ng/syslog-ng_1.9.9-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.
SZALAY Attila <[EMAIL PROTECTED]> (supplier of updated syslog-ng 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, 30 Mar 2006 18:25:11 +0200
Source: syslog-ng
Binary: syslog-ng
Architecture: source i386
Version: 1.9.9-2
Distribution: unstable
Urgency: low
Maintainer: SZALAY Attila <[EMAIL PROTECTED]>
Changed-By: SZALAY Attila <[EMAIL PROTECTED]>
Description: 
 syslog-ng  - Next generation logging daemon
Closes: 324813 352362 355833 356002 357692
Changes: 
 syslog-ng (1.9.9-2) unstable; urgency=low
 .
   * Switch to the latest snapshot version, with some un-released
     upstream bug-fixes. (Closes: #352362)
   * Fixed misspelled KERNEL_RINGBUF_SIZE. Again. (Closes: #324813)
   * Stop syslog-ng when removing. (Closes: #356002)
   * Added some new logckeck lines. (Closes: #357692)
   * Disable statistic messages in default config file. (Closes: #355833)
Files: 
 5e2acbf0e667c08451a127c53573994f 613 admin extra syslog-ng_1.9.9-2.dsc
 21927b2f8f6eb3f01efb1ff21f27ca42 59856 admin extra syslog-ng_1.9.9-2.diff.gz
 45fcf9434e2f91e5eaf5cdfecb7049c1 159998 admin extra syslog-ng_1.9.9-2_i386.deb

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

iD8DBQFELCjL23Gu/Kug6LIRAuivAJ4xQa8zFB7GDouRLDfQEKhAp+/icgCfUeVq
zXiREjK/lbgCMu3dQnvlqGg=
=vNfF
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to