> On Jun 26, 2015, at 4:31 PM, Dennis Peterson wrote:
>
> Try this:
>
> clamconf | fold -s | grep "sysconfdir=/"
>
> That will tell you where clam expects to find your clamd.conf file. That
> might not be where you expect it. Also check the service script to see if
> clamd is started with th
I bet you have a third-party repo in there and there's a 'battle of the
banjos' going on: one repo has clam using clamav and the other using clam
Do what we did. Edit /etc/passwd and make both accounts have the same UID
Problem solved forever ;-)
Jason
On 27/06/15 07:24, Alan Stern wrote:
> On
Try this:
clamconf | fold -s | grep "sysconfdir=/"
That will tell you where clam expects to find your clamd.conf file. That might
not be where you expect it. Also check the service script to see if clamd is
started with the --config-file=FILE option. It will override your compiled
sysconfigdi
On 6/26/2015 14:55, Bob Cohen wrote:
>
>
> Okay. Now I see what happened. The owner and group should be set to
> clamav. And now it works. Thank you. I knew it was something simple.
>
> This makes sense. After a yum update clam sets the log file owner to
> clam:clam instead of clamav:clamav and
> On Jun 26, 2015, at 3:24 PM, Alan Stern wrote:
>
> That's a question for the CentOS-5 maintainers. I suppose you could
> run clamd under the clam userid instead of under clamav. But there
> might be good reasons not to do that, or it might cause other problems.
Thank you again. That’s a goo
On Fri, 26 Jun 2015, Bob Cohen wrote:
> > On Jun 26, 2015, at 2:19 PM, Alan Stern wrote:
> >
> > So what are the permissions for /var/run/clamav? (Does that directory
> > even exist?) And what user/group IDs does your clamd daemon run under?
>
> Thanks for responding:
>
> Yes the directory e
> On Jun 26, 2015, at 2:19 PM, Alan Stern wrote:
>
> So what are the permissions for /var/run/clamav? (Does that directory
> even exist?) And what user/group IDs does your clamd daemon run under?
Thanks for responding:
Yes the directory exists
Permissions:
[root etc]# ls -la /var/run/clamav
On Fri, 26 Jun 2015, Bob Cohen wrote:
> Grr. The yum update breaks my amavisd/clam installation. I’m running CentoOs
> 5.x. It appears to be a permissions problem:
>
> Starting Clam AntiVirus Daemon: ERROR: LOCAL: Socket file
> /var/run/clamav/clamd.sock could not be bound: Permission denied
>
Grr. The yum update breaks my amavisd/clam installation. I’m running CentoOs
5.x. It appears to be a permissions problem:
Starting Clam AntiVirus Daemon: ERROR: LOCAL: Socket file
/var/run/clamav/clamd.sock could not be bound: Permission denied
I’ve reviewed the CentOS Amavisd-new, ClamAV and S
