Hi JR.
Thanks for your response. To clarify, I wasn’t referring to clamd, the daemon, I was referring to clamd, the package, which shows up here (I only have the EPEL and base repos installed): sudo yum install clamav-server … Dependencies Resolved ======================================================================= Package Arch Version Repository Size ======================================================================= Installing: clamd x86_64 0.101.4-1.el7 epel 122 k Installing for dependencies: clamav-filesystem noarch 0.101.4-1.el7 epel 28 k clamav-lib x86_64 0.101.4-1.el7 epel 775 k clamav-update x86_64 0.101.4-1.el7 epel 103 k libtool-ltdl x86_64 2.4.2-22.el7_3 base 49 k pcre2 x86_64 10.23-2.el7 base 201 k Transaction Summary ======================================================================== Install 1 Package (+5 Dependent packages) But not here: sudo yum install clamav … Dependencies Resolved ======================================================================== Package Arch Version Repository Size ======================================================================== Installing: clamav x86_64 0.101.4-1.el7 epel 392 k Installing for dependencies: clamav-filesystem noarch 0.101.4-1.el7 epel 28 k clamav-lib x86_64 0.101.4-1.el7 epel 775 k clamav-update x86_64 0.101.4-1.el7 epel 103 k libtool-ltdl x86_64 2.4.2-22.el7_3 base 49 k pcre2 x86_64 10.23-2.el7 base 201 k Transaction Summary ======================================================================== Install 1 Package (+5 Dependent packages) Regardless, I did a comparison of both installs on clone machines and it turns out the rpm -ql on each (after they’re installed) show the packages do very different things. It appears that the clamav installer contains the clamav package which includes the clambc, clamconf, clamdscan, clamdtop, clamscan, clamsubmit and sigtool binaries (along with various support files) but NOT the clamd daemon binary while the clamav-server installer contains the clamd package which contains the clamd binary. This was the source of my original concerns and why I emailed the list in the first place. When I followed the instructions in the RHEL / CentOS section of https://www.clamav.net/documents/installing-clamav that stated (after the epel-release install) that “yum install -y clamav” was all that was needed to install ClamAV but that process doesn’t leave a clamd daemon anywhere on the system I started looking around the web to see how other people had done it, finding the “yum -y install clamav-server clamav-data clamav-update clamav-filesystem clamav clamav-scanner-systemd clamav-devel clamav-lib clamav-server-systemd” proposed kitchen-sink installer command, prompting me to email this list and see if anyone had any more detail on what packages did what and seeing if anyone had any suggestions on how to do a usable install because without clamd in the clamav installer and package, the install instructions in the documentation on clamav.net don’t work to produce a usable installation. I think at this point I have a better understanding of the ClamAV related installers in the EPEL repository and will go do some testing of my use cases. Oh, and I definitely don’t intend to actually set up scanning from /. I was just looking for ideas as to what should be avoided and why. :) Thanks for your feedback, Scott
_______________________________________________ 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
