On October 20, 2017 5:36:12 PM EDT, Zetan Drableg <[email protected]> wrote: >Hi, I'm building and packaging clamav in a RPM for distribution to some >systems without EPEL access. >While it installs ok, the default paths are absolute paths of my build >server, not of the client system. > >tar xvzf clamav-0.99.2.tar.gz >cd clamav-0.99.2 >./configure --prefix="/usr" --with-dbdir=/var/lib/clamav >make -j 4 >make install DESTDIR=$OUT > >bundle as rpm with FPM > >fpm \ > --input-type dir \ > --output-type rpm \ > --name "clamav" \ > --package "$OUT/../" \ > --version "0.99.2-$BUILD" \ > --iteration xyz_$BUILD \ > --rpm-user root \ > --rpm-group root \ > --description "ClamAV 0.99.2" \ > --prefix / \ > -C "$OUT" \ > -a x86_64 \ > usr > > >freshclam >ERROR: Can't open/parse the config file >/var/bamboo/xml-data/build-dir/CLAM-CLAMAV-JOB1/out/etc/freshclam.conf > >/usr/bin/freshclam --config-file=/etc/freshclam.conf >works as expected > >Any tips which configure option controls default path to >freshclam.conf?
Add --sysconfdir=/etc/clamav (or whatever path you prefer) to your configure arguments. Scott K _______________________________________________ clamav-users mailing list [email protected] http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
