Package: dsyslog
Version: 0.5.0
Severity: normal

sysklogd, syslog-ng and other loggers print the pid file on each log line 
between brackets, like this:

Apr 30 07:57:53 labs sshd[22760]: pam_unix(sshd:session): session closed for 
user micah
Apr 30 08:00:51 labs postfix/cleanup[25008]: 7A69D271BD6: 
message-id=<[email protected]>
Apr 30 08:00:52 labs postfix/smtp[25010]: 7A69D271BD6: to=<[email protected]>, 
relay=mx1.riseup.net[0.0.0.0]:25, delay=0.61, delays=0.17/0.01/0.3/0.12, 
dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as DCEC05715D3)

but dsyslog omits the PID:

Apr 30 07:21:30 labs postfix/smtp: 24908271BD6: to=<[email protected]>, 
relay=mx1.riseup.net[0.0.0.0]:25, delay=2, delays=0.16/0.01/0.21/1.6, 
dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 70733571EA6)

Without the [$PID] dsyslog generates logs that are incompatible with
all of the logcheck rules, which would inhibit anyone who uses
logcheck from wanting to use dsyslog at all.

micah


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-vserver-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages dsyslog depends on:
ii  libc6                         2.9-7      GNU C Library: Shared libraries
ii  libglib2.0-0                  2.20.1-1   The GLib library of C routines
ii  libgnutls26                   2.6.5-1    the GNU TLS library - runtime libr

Versions of packages dsyslog recommends:
ii  logrotate                     3.7.7-3    Log rotation utility

Versions of packages dsyslog suggests:
pn  dsyslog-module-gnutls         <none>     (no description available)
pn  dsyslog-module-mysql          <none>     (no description available)
pn  dsyslog-module-postgresql     <none>     (no description available)

-- no debconf information



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

Reply via email to