Abdul Rehman Gani wrote:
Hi,
Clamscan currently detects Exploit.WMF.A, but F-Secure are reporting 57
different varieties. How many does this signature detect?
Just an update:
I believe that with daily.cvd version 1225, you can expect (almost)
complete detection of WMF exploits.
Current
I am trying to change the temporary directory for clamav but the change is
not working clamav is still writing to /tmp.
My clamd.conf
LogFile /var/log/clamav/clamd.log
LogFileMaxSize 5M
LogTime
TemporaryDirectory /var/clamavtmp/tmp
DatabaseDirectory /var/lib/clamav
TCPAddr 127.0.0.1
TCPSocket 33
* On 03/01/06 09:57 -0500, Brian McDonald wrote:
>
> I am trying to change the temporary directory for clamav but the change is
> not working clamav is still writing to /tmp.
>
> My clamd.conf
>
> LogFile /var/log/clamav/clamd.log
> LogFileMaxSize 5M
> LogTime
> TemporaryDirectory /var/clamavtmp
You will have to explain what you mean by "HUP the process"
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Odhiambo
Washington
Sent: Tuesday, January 03, 2006 10:04 AM
To: clamav-users@lists.clamav.net
Subject: Re: [Clamav-users] clamd.conf not recognizing
On Tue, 2006-01-03 at 10:06 -0500, Brian McDonald wrote:
> You will have to explain what you mean by "HUP the process"
kill -SHUP clamd
In other words, clamd only reads clamd.conf at process start time, or
when it receives the HUP signal. So, if clamdscan is causing activity
in /tmp, and clamd h
I restarted clamd using service clamd restart I also tried service clamd
stop and service clamd start but clamd is still writing to the /tmp
What is the differnece between clamscan and clamdscan
Sorry for the questions but I am a newbie to clamav
-Original Message-
From: [EMAIL PROTECT
He means restart the clamd server application...
HUP is the kill signal that gets sent to a process to tell it to shut
everything down.
HUP
The following command
$ kill -s SIGHUP 1001
sends the HUP or hang-up signal to the program that is running with process ID
1001. You can also use t
On 03/01/06, Brian McDonald <[EMAIL PROTECTED]> wrote:
> I restarted clamd using service clamd restart I also tried service clamd
> stop and service clamd start but clamd is still writing to the /tmp
Are you sure you're changing the clamd.conf file that the installed
version of clamd is using? Tr
>> I restarted clamd using service clamd restart I also tried service clamd
>> stop and service clamd start but clamd is still writing to the /tmp
>Are you sure you're changing the clamd.conf file that the installed
>version of clamd is using? Try:
>find / -name "clamd.conf" -print
>You should o
