Your message dated Tue, 05 Oct 2021 07:39:08 -0400
with message-id <a3f1a5de6087230f831b6a5838bf5b51ce7b9348.ca...@debian.org>
and subject line Re: obnam does not include program name in syslog messages
has caused the Debian Bug report #682662,
regarding obnam does not include program name in syslog messages
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
682662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682662
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: obnam
Version: 1.1-1
Severity: normal
Dear Maintainer,
I am logging with the following setup in my configfile:
log = syslog
log-level = info
The log-messages received by rsyslogd and stored into /var/log/syslog look
the following:
Jul 24 04:23:03 vpnhub1 2012-07-24 04:23:03 INFO Backup starts
Jul 24 04:23:03 vpnhub1 2012-07-24 04:23:03 INFO Checkpoints every 1073741824
bytes
Could you please include the program name (optional with pid) as every
standard syslog client does?
Calling it INFO / DEBUG makes it very difficult to create clean logcheck
rules for it.
Thanks,
Haegar
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages obnam depends on:
ii libc6 2.13-34
ii python 2.7.3-1
ii python-cliapp 1.20120630-1
ii python-larch 1.20120527-1
ii python-paramiko 1.7.7.1-3
ii python-tracing 0.6-2
ii python-ttystatus 0.19-1
obnam recommends no packages.
obnam suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.20140719-1
Mark this bug as done since the bug has been fixed in all supported Debian
releases (sid, testing, stable, oldstable) as of Oct 2021.
Thanks,
Boyuan Yang
On Tue, 24 Jul 2012 14:36:06 +0200 Haegar <hae...@vpnhub1.hamburg.ccc.de>
wrote:
> Package: obnam
> Version: 1.1-1
> Severity: normal
>
> Dear Maintainer,
>
> I am logging with the following setup in my configfile:
>
> log = syslog
> log-level = info
>
> The log-messages received by rsyslogd and stored into /var/log/syslog look
> the following:
>
> Jul 24 04:23:03 vpnhub1 2012-07-24 04:23:03 INFO Backup starts
> Jul 24 04:23:03 vpnhub1 2012-07-24 04:23:03 INFO Checkpoints every
1073741824 bytes
>
> Could you please include the program name (optional with pid) as every
> standard syslog client does?
>
> Calling it INFO / DEBUG makes it very difficult to create clean logcheck
> rules for it.
>
> Thanks,
> Haegar
>
> -- System Information:
> Debian Release: wheezy/sid
> APT prefers unstable
> APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
> Architecture: i386 (i686)
>
> Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores)
> Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
> Shell: /bin/sh linked to /bin/dash
>
> Versions of packages obnam depends on:
> ii libc6 2.13-34
> ii python 2.7.3-1
> ii python-cliapp 1.20120630-1
> ii python-larch 1.20120527-1
> ii python-paramiko 1.7.7.1-3
> ii python-tracing 0.6-2
> ii python-ttystatus 0.19-1
>
> obnam recommends no packages.
>
> obnam suggests no packages.
>
> -- no debconf information
>
>
signature.asc
Description: This is a digitally signed message part
--- End Message ---
