Check out the clamav.conf file... In the file, there are two locations 
you want to check...

The first entry is LocalSocket it set to /tmp/clamd by default. Set this 
to somewhere that clamd can write to with its UID/GID. /tmp is the best, 
but that requires perms to /tmp.

The second entry is TCPSocket, it's simply a number set 3310 by default. 
If 3310 is already in use by another program, and you wish to use it as 
a TCP based virus server, then change this to something else that you 
know can be accessed by other machines, etc, but unless clamd is being 
run as root, which in your case, it is not, definately don't go below 
1024.... You likely do not use this, so just make sure its commented 
out... It's kind of a useless feature unless you're doing something real 
bizarre with clamd.

Best thing to do is change the UID/GID that clamd is running under.... I 
have clamd running as it's own user with UID/GID at 102/102, my perms 
for /tmp are 777 owned by root.root and perms for /var/run are 755 
root.root as well. my clamav user is also in the root group, allwing me 
to give it more without letting perms go... Just make sure not to let 
the clamav user log in... ;-)

Thus clamav runs with priveleged permissions, and has access to lots of 
things that it needs in order to run right...

Brian Read wrote:

> At 20:15 27/12/2002, you wrote:
>
>> On Fri, 27 Dec 2002 12:38:11 -0700
>> Matt Blecha <[EMAIL PROTECTED]> wrote:
>>
>> > Here's another question... Does the qmailq user have perms to bind to
>> > unix or tcp sockets, if it can't bind a unix or tcp socket, that would
>> > be why the crash happens... clamd does not do very good error 
>> reporting
>>
>> There was no crash, just an error and exit. clamd don't log to the 
>> console,
>> because it detaches from it just after dropping the privileges. I think
>> you're reight, and this is a permission problem. Brian, try to change
>> the TCPSocket value.
>
>
> You'll have to give me some details of what to do, I am out of my 
> depth here.
>
> cheers
>
> Brian
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Reply via email to