yes, it seems that Ubuntu changes ClamAV really much, some other log entries 
also missing here, in the original Software they are included ...

Von / From:     Orion Poplawski Via Clamav-Users 
<mailto:[email protected]>
An / To:        Newcomer01 <mailto:[email protected]>
CC / CC:        Orion Poplawski <mailto:[email protected]>
Gesendet / Sent:        Freitag, Oktober 03, 2025 um 20:05 (at 08:05 PM) +0200
Betreff / Subject:      [clamav-users] question about freshclam log output

On EL9 with clamav 1.4.3-2.el9 freshclam in daemon mode reports:

Received signal: wake up
ClamAV update process started at Fri Oct  3 09:09:56 2025
daily.cld database is up-to-date (version: 27780, sigs: 2076928, f-level: 90,
builder: tomjudge)
main.cvd database is up-to-date (version: 62, sigs: 6647427, f-level: 90,
builder: sigmgr)
bytecode.cvd database is up-to-date (version: 339, sigs: 80, f-level: 90,
builder: nrandolp)
--------------------------------------
Received signal: wake up
ClamAV update process started at Fri Oct  3 11:09:56 2025
daily.cld database is up-to-date (version: 27780, sigs: 2076928, f-level: 90,
builder: tomjudge)
main.cvd database is up-to-date (version: 62, sigs: 6647427, f-level: 90,
builder: sigmgr)
bytecode.cvd database is up-to-date (version: 339, sigs: 80, f-level: 90,
builder: nrandolp)
--------------------------------------


On Ubuntu 22.04.5 with clamav 1.4.3+dfsg-0ubuntu0.22.04.1 freshclam in daemon
mode we see:


daily.cld database is up-to-date (version: 27779, sigs: 2076925, f-level: 90,
builder: raynman)
main.cld database is up-to-date (version: 62, sigs: 6647427, f-level: 90,
builder: sigmgr)
bytecode.cld database is up-to-date (version: 339, sigs: 80, f-level: 90,
builder: nrandolp)
daily.cld database is up-to-date (version: 27779, sigs: 2076925, f-level: 90,
builder: raynman)
main.cld database is up-to-date (version: 62, sigs: 6647427, f-level: 90,
builder: sigmgr)
bytecode.cld database is up-to-date (version: 339, sigs: 80, f-level: 90,
builder: nrandolp)
--------------------------------------
daily.cld database is up-to-date (version: 27779, sigs: 2076925, f-level: 90,
builder: raynman)
main.cld database is up-to-date (version: 62, sigs: 6647427, f-level: 90,
builder: sigmgr)
bytecode.cld database is up-to-date (version: 339, sigs: 80, f-level: 90,
builder: nrandolp)
--------------------------------------


So:

Ubuntu does not output the "ClamAV update process started at DATE" message,
and also does not apppear to always output the "---" delimiter.  It's the date
message that is of concern to use due to logwatch trying to parse it.

The freshclam.conf files are essentially identical.  Any idea what might cause
this difference?


_______________________________________________

Manage your clamav-users mailing list subscription / unsubscribe:
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/Cisco-Talos/clamav-documentation

https://docs.clamav.net/#mailing-lists-and-chat
_______________________________________________

Manage your clamav-users mailing list subscription / unsubscribe:
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/Cisco-Talos/clamav-documentation

https://docs.clamav.net/#mailing-lists-and-chat

Reply via email to