Bug 906461

Summary: wrong default pidfile in /etc/clamd.d/amavisd.conf
Product: [Fedora] Fedora EPEL Reporter: Robert Moskowitz <rgm>
Component: amavisd-newAssignee: Juan Orti <jorti>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: el6CC: janfrode, jorti, perl-devel, steve, strobert, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-27 14:00:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Robert Moskowitz 2013-01-31 16:50:00 UTC 
Description of problem:

The default pidfile for clamd in /etc/clamd.d/amavisd.conf does not default pidfile in /etc/clamd.conf

Version-Release number of selected component (if applicable):


amavisd-new-2.6.4-2.el6.noarch.rpm

as compared to

clamd-0.97.6-1.el6.i686.rpm

How reproducible:

very

Steps to Reproduce:
1. install amavisd-new and clamd
2. inspect .conf files
3.
  
Actual results:

/etc/clamd.d/amavisd.conf has the pidfile of

/var/run/amavisd/clamd.pid

whereas /etc/clamd.conf has the pidfile of

/var/run/clamav/clamd.pid


Expected results:

Defaults should match

Additional info:
Comment 1 Steven Roberts 2013-01-31 19:09:04 UTC 
Happened to see this go by on the IRC channel.  FYI, I think the PID in /etc/clamd.conf is for the clamd service whereas /etc/clamd.d/amavisd.conf is for clamd.amavis.

we have clamd.amavis running and clamd not running.

this is on RHEL5
Comment 2 Robert Moskowitz 2013-01-31 20:00:33 UTC 
chkconfig shows both daemons, clamd and clamd.amavisd

clamd is set to start at boot; this is the one I have been restarting after various changes.

And when I do 'service _____ status' I get the same pid for both daemons!

Definitely need this cleared up, it seems?  if /etc/clamd.d/amavisd.conf is for clamd.amavis the comments there should say so.
Comment 3 Steven Roberts 2013-01-31 22:10:19 UTC 
Interesting.  I show both in chkconfig, but I have clamd disabled in chkconfig and clamd.amavis enabled and that is the one that is running and I restart.

definitely sounds like some docs/comments in a config file may need updating.  I'm now wondering if how I am running is "correct" :)
Comment 4 Robert Moskowitz 2013-01-31 22:32:27 UTC 
For me it is the opposite.

Do a 'service clamd status' and 'service clamd.amavis status' and see what you get.

I installed amavisd-new clamav clamav-devel clamd & spamassassin

I used http://wiki.centos.org/HowTos/Amavisd as guidelines but used epel rather than rpmforge.  And this is on Centos 6.3, so things COULD be a little different with RHEL5 compared to RHEL6.

Oh, and I edited the pidfile in /etc/clamd.d/amavisd.conf for clamd to match what is in /etc/clamd.conf
Comment 5 Juan Orti 2014-06-27 14:00:13 UTC 
It looks like you are confusing those two services.

Amavis drops a clamd configuration file in /etc/clamd.d/amavisd.conf and an init script to start and stop its own clamd instance.
That instance is different from the one provided by clamd itself, and they can be started/stopped independently of each other.

I hope to have helped you.