* Gergely Nagy alger...@balabit.hu, 2013-11-21, 14:42:
Hm... I have not been able to reproduce it yet...
I suspect the bug might be architecture-specific. I can reproduce it on i386,
but not on amd64.
can you change your template to include ${.linux.timestamp} too, and send me a
sample?
Control: tag -1 upstream
Found the issue, I'm pushing a fix into git, fixed package should hit
unstable early next week latest. Thanks for the report and the
assistance!
--
|8]
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
Jakub Wilk jw...@debian.org writes:
* Gergely Nagy alger...@balabit.hu, 2013-11-15, 17:05:
syslog-ng has just logged this:
1961-02-05T20:15:59+01:00 borsuk kernel: usb 1-2: USB disconnect, device
number 5
The timestamp is obviously bogus. My system date is correct, and
non-kernel messages
Jakub Wilk jw...@debian.org writes:
* Gergely Nagy alger...@balabit.hu, 2013-11-21, 14:42:
Hm... I have not been able to reproduce it yet...
I suspect the bug might be architecture-specific. I can reproduce it
on i386, but not on amd64.
Mhm, great, then I have a suspicion where the problem
Jakub Wilk jw...@debian.org writes:
Package: syslog-ng-core
Version: 3.5.1-1
syslog-ng has just logged this:
1961-02-05T20:15:59+01:00 borsuk kernel: usb 1-2: USB disconnect, device
number 5
The timestamp is obviously bogus. My system date is correct, and
non-kernel messages are logged
* Gergely Nagy alger...@balabit.hu, 2013-11-15, 17:05:
syslog-ng has just logged this:
1961-02-05T20:15:59+01:00 borsuk kernel: usb 1-2: USB disconnect, device number
5
The timestamp is obviously bogus. My system date is correct, and non-kernel
messages are logged with correct timestamps.
Package: syslog-ng-core
Version: 3.5.1-1
syslog-ng has just logged this:
1961-02-05T20:15:59+01:00 borsuk kernel: usb 1-2: USB disconnect, device number
5
The timestamp is obviously bogus. My system date is correct, and non-kernel
messages are logged with correct timestamps.
According to
7 matches
Mail list logo
