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
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
