On Jul 31, 2013, at 7:31 PM, Bob Miller wrote:
> Hello,
>
>>> I realize seeing this that the list rules are not to top post, yet my
>>> very first reply to this list that is exactly what I did.
>>
>> What list rules would that be?
>>
>>
>> -Al-
>
> This is the content of the mail I received
Hello,
> > I realize seeing this that the list rules are not to top post, yet my
> > very first reply to this list that is exactly what I did.
>
> What list rules would that be?
>
>
> -Al-
This is the content of the mail I received upon having my subscription
to this list approved, the last en
On Jul 31, 2013, at 1:22 PM, Bob Miller wrote:
>
> I realize seeing this that the list rules are not to top post, yet my
> very first reply to this list that is exactly what I did.
What list rules would that be?
-Al-
--
Al Varnell
Mountain View, CA
___
Hi Dennis,
Many thanks for the time you took to reply. Though I have had any
epiphanies yet, talking the situation over definitely helps...
> Running clamd as root is probably a bad idea but I can imagine a lot of
> debate I'm not interested in rising from that statement.
If I understand this
Running clamd as root is probably a bad idea but I can imagine a lot of
debate I'm not interested in rising from that statement. It is not
something I would do. When I hit this problem of allowing clamd and my
milters to share that and other sockets I put them all in the same
UID/GID (not root)
Thank you very much for taking the time to respond. It is truly
appreciated...
I was able to make your suggestion work by removing the following two
lines from clamd.conf:
User clamav
LocalSocketGroup simscan
which creates the socket thusly:
srw-rw 1 root root0 Jul 31 10:04 clamd.socke
Hi there,
On Wed, 31 Jul 2013, Bob Miller wrote:
Thanks for any thoughts you wish to share...
Set the owner of the socket to root, and then repeat your tests.
--
73,
Ged.
___
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
