martinnitram wrote:
> if you used /etc/rc.d/init.d/clamav-milter to start the milter, at around
> line 20, you can see
>
> ...
> # Local clamav-milter config
> CLAMAV_FLAGS=
> test -f /etc/sysconfig/clamav-milter && . /etc/sysconfig/clamav-milter
> ...
>
> so the milter config file should be "/et
martinnitram wrote:
> if you used /etc/rc.d/init.d/clamav-milter to start the milter, at around
> line 20, you can see
>
> ...
> # Local clamav-milter config
> CLAMAV_FLAGS=
> test -f /etc/sysconfig/clamav-milter && . /etc/sysconfig/clamav-milter
> ...
>
> so the milter config file should be "/etc/
if you used /etc/rc.d/init.d/clamav-milter to start the milter, at around
line 20, you can see
...
# Local clamav-milter config
CLAMAV_FLAGS=
test -f /etc/sysconfig/clamav-milter && . /etc/sysconfig/clamav-milter
...
so the milter config file should be "/etc/sysconfig/clamav-milter"
hope helpfu
Nigel Horne wrote:
> Notifications of ClamAV signature updates are now available via our
> Twitter feed at http://twitter.com/clamav.
Just to add Sanesecurity updates are also available on Twitter, showing
all updates to the signatures, since July: http://twitter.com/sanesecurity
__
Hello list
Long time since I was around here, but I have continued running Clamav
anyway and I have been happy until today.
On a very old OS (FreeBSD-5.5) I have always successfully compiled Clamav
from the ports by editing the ports Makefile and changing
--enable-gethostbyname_r to --disable-geth
