Your message dated Sun, 21 Oct 2007 21:02:02 +0000 with message-id <[EMAIL PROTECTED]> and subject line Bug#409620: fixed in syslog-ng 2.0.5-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: 2.0.0-1 Severity: normal Subject: syslog-ng: Does not print program name Package: syslog-ng Version: 2.0.0-1 Severity: normal As opposed to sysklogd-1.4.1-18, syslog-ng2.0.0-1 does not print the program name for "gconfd" (and maybe other programs) (both packages with default configuration): ,----[ /var/log/messages, written by sysklogd (wrapped) ]--- | | Feb 4 12:57:34 pc9 gconfd (mjk-unsafe-5403): starting (version 2.16.0), pid 540 | 3 user 'mjk-unsafe' | Feb 4 12:57:35 pc9 gconfd (mjk-unsafe-5403): Resolved address "xml:readonly:/et | c/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0 [...] | Feb 4 12:58:20 pc9 gconfd (mjk-unsafe-5403): Exiting | `---- ,----[ /var/log/messages, written by syslog-ng (wrapped)]--- | | Feb 4 13:02:20 pc9 (mjk-unsafe-6439): starting (version 2.16.0), pid 6439 user | 'mjk-unsafe' | Feb 4 13:02:20 pc9 (mjk-unsafe-6439): Resolved address "xml:readonly:/etc/gconf | /gconf.xml.mandatory" to a read-only configuration source at position 0 [...] | Feb 4 13:02:31 pc9 (mjk-unsafe-6439): Exiting | `---- The difference can be easily seen in a direct juxtaposition: sysklogd : Feb 4 12:58:20 pc9 gconfd (mjk-unsafe-5403): Exiting syslog-ng: Feb 4 13:02:31 pc9 (mjk-unsafe-6439): Exiting Using the template template("$ISODATE $HOST [$FACILITY:$LEVEL] \tPROG: $PROGRAM, PID: $PID, MSG: $MSG\n"); the output looks like this: ,----[ /var/log/messages, written by syslog-ng with a template (wrapped) ]--- | | 2007-02-04T13:15:31+01:00 pc9 [syslog:notice] PROG: syslog-ng, PID: 5893, MSG: | syslog-ng[5893]: SIGHUP received, reloading configuration; | 2007-02-04T13:15:45+01:00 pc9 [user:info] PROG: (mjk-unsafe-8674), PID: , | MSG: (mjk-unsafe-8674): Exiting | 2007-02-04T13:15:52+01:00 pc9 [user:info] PROG: (mjk-unsafe-9003), PID: , | MSG: (mjk-unsafe-9003): starting (version 2.16.0), pid 9003 user 'mjk-unsafe' | `---- Strangely enough, the process that's called "gconfd" in sysklogd's output is actually shown as /usr/lib/libgconf2-4/gconfd-2 in ps's output. To get repeated outputs of gconfd, I started firefox && gconftool --shutdown after (re-)installing each sys*log* package. And after re-installing sysklogd, I killed syslog-ng manually (that's probably a bug in a postinst or prerm script which I'll report separately). I chose severity "normal", as the missing program name can make debugging difficult if the logged program is not in memory anymore, so that it cannot be found by the displayed PID anymore. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-686 Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15) Versions of packages syslog-ng depends on: ii libc6 2.3.6.ds1-10 GNU C Library: Shared libraries Versions of packages syslog-ng recommends: ii logrotate 3.7.1-3 Log rotation utility -- no debconf information -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-686 Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15) Versions of packages syslog-ng depends on: ii libc6 2.3.6.ds1-10 GNU C Library: Shared libraries Versions of packages syslog-ng recommends: ii logrotate 3.7.1-3 Log rotation utility -- no debconf information
--- End Message ---
--- Begin Message ---Source: syslog-ng Source-Version: 2.0.5-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_2.0.5-2.diff.gz to pool/main/s/syslog-ng/syslog-ng_2.0.5-2.diff.gz syslog-ng_2.0.5-2.dsc to pool/main/s/syslog-ng/syslog-ng_2.0.5-2.dsc syslog-ng_2.0.5-2_i386.deb to pool/main/s/syslog-ng/syslog-ng_2.0.5-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: Sun, 21 Oct 2007 22:42:09 +0200 Source: syslog-ng Binary: syslog-ng Architecture: source i386 Version: 2.0.5-2 Distribution: unstable Urgency: low Maintainer: SZALAY Attila <[EMAIL PROTECTED]> Changed-By: SZALAY Attila <[EMAIL PROTECTED]> Description: syslog-ng - Next generation logging daemon Closes: 409620 419165 436521 Changes: syslog-ng (2.0.5-2) unstable; urgency=low . * Changed init information printing method to lsb. (applied the patch from Michael Biebl <[EMAIL PROTECTED]>) (Closes: #419165) * When removing syslog-ng stop it in prerm. (Closes: #436521) * Added a new option into the default config to circumvent a logging bug in gconfd. (Closes: #409620) Files: 35fc01ebd6a7ee7c6037d3e8abf6cfdc 620 admin extra syslog-ng_2.0.5-2.dsc 91d10176ea3710c1676dc5cc6ed8be93 11037 admin extra syslog-ng_2.0.5-2.diff.gz 8b70fd4f60b1ca8c5d654ab0e7829d18 186328 admin extra syslog-ng_2.0.5-2_i386.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHG7zz23Gu/Kug6LIRArNFAJ9r6tgQ6xZgdr27sY7vhenwGRRPbACgojUF aCzrUqw4aYarFfPFzQ66ZwI= =dVx8 -----END PGP SIGNATURE-----
--- End Message ---
