On Sat, Mar 07, 2026 at 09:57:30PM +0100, Lorenzo wrote: Hi,
> <[email protected]> wrote: > > Package: socklog > > Version: 2.1.0-8 > > Severity: wishlist > > > > Hi, > > > > when logging kernel messages over UDP with socklog+svlogd, the end > > result looks like this: > > > > @400000004986304d23ededec 172.18.17.254: @400000004986304d23676c54 > > kern.warn: Feb 2 00:29:07 kernel: ... > > > > The line contains three timestamps, which is not very useful and only > > makes the message harder to read. > > [ snip ] > > > > > 1. Adding a new config command to "send via UDP without timestamp". > > [16 years later] 17, even :) > > My current workaround involves syslog-ng, and is much heavier than > > ideal. > > In case this is still relevant now, could you please take a look at the > patch that was recently merged in upstream next branch at > > https://github.com/g-pape/socklog/pull/6 > > https://github.com/g-pape/socklog/commit/a2bc68f1e46693d76500405489832ef7b9096bf0 > > and tell if it would fix this bug? (I think it does) It fixes part of the "bug": instead of 3, we'd have 2 timestamps on each line -- one tai64n generated by the client, one by the server. ("Bug" in quotation marks because it's really more a feature request.) > I can add the patch to the Debian package in case a new release doesn't > happen soon. I'm using syslog-ng in these situations, so while I approve of this change in general terms, it wouldn't have an immediate impact for me. I appreciate the offer to backport the patch, but there is no need. Thanks! András -- The trouble with political humor is that so many jokes are elected.
