Hi Sun,

Main.cld is the decompressed version of main.cvd.  The .cld version is 
generated when the .cvd version gets an update using .diff update files.  It is 
a more efficient mechanism than downloading the entire database to update.  
This is most common with the daily database, and less common with the bytecode 
and main databases.

It’s possible to get the databases either on your webserver or ClamAV clients 
in a state where it has both .cld and .cvd files, particularly when configuring 
a private mirror.  For the client, you would see a complaint about the 
duplicate databases because it knows you only need one.

We have some documentation on setting up private local mirrors here: 
http://www.clamav.net/documents/private-local-mirrors
Truthfully I am less familiar with setting up private mirrors than others on 
the list, so if you have any specific questions, some others may chime in.

Cheers,
Micah

Micah Snyder
ClamAV Development
Talos
Cisco Systems, Inc.


From: clamav-users <clamav-users-boun...@lists.clamav.net> on behalf of Sunhux 
G via clamav-users <clamav-users@lists.clamav.net>
Reply-To: ClamAV users ML <clamav-users@lists.clamav.net>
Date: Monday, February 25, 2019 at 10:05 AM
To: ClamAV users ML <clamav-users@lists.clamav.net>
Cc: Sunhux G <sun...@gmail.com>
Subject: [clamav-users] PrivateMirror : freshclam messages

Our setup:
1) have freshclam download via Internet on a Solaris 10 x86 server in DMZ
2) an ex-colleague who left us served out cvd/cld via httpd on this Solaris 
server
3) have internal RHEL7 freshclam try to update from that Solaris httpd server 
using the private mirror

In the internal RHEL7's, /etc/freshclam.conf  line:
   PrivateMirror that_Solaris_hostname
& in RHEL7's  /etc/hosts
   IP_of_Solaris   that_Solaris_hostname

On RHEL7, when we ran 'freshclam', got the messages below:
[root@frclamclient etc]# freshclam
ClamAV update process started at Mon Feb 25 17:10:03 2019
Reading CVD header (main.cld): WARNING: main.cld not found on remote server   
<== is this crucial??
Reading CVD header (main.cvd): OK
main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder: 
sigmgr)
Reading CVD header (daily.cld): OK
daily.cld is up to date (version: 25370, sigs: 2259916, f-level: 63, builder: 
raynman)
Reading CVD header (bytecode.cld): OK
bytecode.cvd is up to date (version: 328, sigs: 94, f-level: 63, builder: neo)


Are we missing something with main.cld??

Thanks
Sun
_______________________________________________

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Reply via email to