@heynnema was driving the discussion upstream (thanks!): https://sourceforge.net/p/logwatch/discussion/1115929/thread/4af80708f6/
But it seems to have stalled and we should probably file a bug report with upstream logwatch about the change in ClamAV's output of "ClamAV update process started at Mon Jul 15 06:28:54 2024" => "Mon Jul 15 06:28:54 2024 -> ClamAV update process started at Mon Jul 15 06:28:54 2024" (as stated in comment #15), which should be adopted upstream. https://sourceforge.net/p/logwatch/bugs/ Besides that, the workaround for now seems to be reading from journalctl instead of "freshclam.log", e.g. by using this configuration in /etc/logwatch/conf/services/clam-update.conf, as described in comment #26: """ LogFile = LogFile = none *JournalCtl = "--output=cat --unit=clamav-freshclam.service" """ See also https://www.usebox.net/jjm/blog/logwatch-and-systemd-journal/. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067608 Title: clamav-freshclam 1.0.5 and logwatch 7.7-1 fails to report To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/2067608/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
