Al
Take the C out for starting unless you are jailing the
process. It should start fine.
--- al [EMAIL PROTECTED] wrote:
After building the FreeBSD 0.91.2 port to replace
0.88.5, the milter
shuts down as soon as it starts. Here is the
forground output:
blackwidow#
al wrote:
After building the FreeBSD 0.91.2 port to replace 0.88.5, the milter
shuts down as soon as it starts. Here is the forground output:
blackwidow# /usr/local/sbin/clamav-milter -CNqlo /var/run/clmilter.sock
WARNING: /usr/local/sbin/clamav-milter: running as root is not
The Nqlo: No
I seem to recall I have come across this before, but I just can't find
it. Maybe someone knows off-hand. :)
When using additional, third party signatures, is there any particular
order in the signatures? If both, the official as well as the third
party sigs match, which one is being reported?
It appears that if clamuko is configured to scan a particular directory on
access, then clamscan does not actually identify the file as an infected file.
The results of the clamscan show Infected files: 0, even though the directory
has an infected file (in this case, eicar for testing). In
At 12:37 PM 10/22/2007, Karsten Bräckelmann wrote:
When using additional, third party signatures, is there any particular
order in the signatures?
No particular order.
If both, the official as well as the third
party sigs match, which one is being reported?
One or the other will be reported,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Oct 21, 2007 at 08:50:17AM -0700, P T wrote:
I downloaded clam av from the clam av site. However when I check the
signature I get that basically it isn't a trusted signature. How am I doing
this wrong?
# to get the key
gpg --keyserver
On Mon, 2007-10-22 at 14:43 -0500, Noel Jones wrote:
At 12:37 PM 10/22/2007, Karsten Bräckelmann wrote:
When using additional, third party signatures, is there any particular
order in the signatures?
No particular order.
If both, the official as well as the third
party sigs match, which
