Your message dated Tue, 6 May 2025 18:09:30 +0200
with message-id <[email protected]>
and subject line Re: Bug#1101458: rsyslog: no kernel timestamps in kernel logs 
by default since v8.2312
has caused the Debian Bug report #1101458,
regarding rsyslog: no kernel timestamps in kernel logs by default since v8.2312
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 [email protected]
immediately.)


-- 
1101458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101458
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: rsyslog
Version: 8.2406.0-1ubuntu2
Severity: wishlist

Dear Maintainer,

Since version v8.2312 of rsyslog the kernel timestamp are omitted by default in
the kernel logs due to the fix of[1]. This is a useful feature for
investigating kernel issues and it woudl be nice to have it enabled by default.
Would it be possible to update debian/rsyslog.conf to set
keepkerneltimestamp="on".


[1] https://github.com/rsyslog/rsyslog/issues/5160


-- System Information:
Debian Release: trixie/sid
  APT prefers oracular-updates
  APT policy: (500, 'oracular-updates'), (500, 'oracular-security'), (500, 
'oracular'), (100, 'oracular-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.11.0-21-generic (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--- End Message ---
--- Begin Message ---
Hi Vladimir,

thanks for raising this issue on debian-devel. It appears this hasn't sparked any real interest.

As a result, I've raised the same issue again on the #debian-devel IRC channel with the same results: no response.

My conclusion is, that people don't care and as a consequence I would just go with what upstream is doing, i.e. there is no compelling argument to deviate it downstream in Debian.


Regards,
Michael

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to