Yep. That's fine. /tmp or /var/tmp (or /run) is usually where it goes
anyway. Welcome to the ClamAV club :)
On Mon, Aug 20, 2018 at 7:45 PM Michael Newman wrote:
>
> On Aug 20, 2018, at 23:00, *Maarten Broekman* wrote:
>
>
> For clamdscan to work you need to enable LocalSocket at the very
> On Aug 20, 2018, at 23:00, Maarten Broekman wrote:
>
> For clamdscan to work you need to enable LocalSocket at the very least.
Thank you. I had no idea what a socket was. Now I know.
I didn’t know where to put it, so I tried this:
LocalSocket /var/tmp/clamd.socket
It seems to have worked
For clamdscan to work you need to enable LocalSocket at the very least.
On Mon, Aug 20, 2018 at 5:32 PM Michael Newman wrote:
>
> On Aug 20, 2018, at 23:00, Al Varnell wrote:
>
>
> Please post the results of the following Terminal Command:
>
> sudo clamconf
>
>
> MrMuscle:~ mnewman$ sudo
> On Aug 20, 2018, at 23:00, Al Varnell wrote:
>
> Please post the results of the following Terminal Command:
>
> sudo clamconf
MrMuscle:~ mnewman$ sudo clamconf
Password:
Checking configuration files in /opt/local/etc
Config file: clamd.conf
---
BlockMax disabled
Hello,
Am 20.08.2018 um 13:05 schrieb Matus UHLAR - fantomas:
On 20.08.18 17:55, Michael Newman wrote:
clamd is running:
MrMuscle:~ mnewman$ ps -A | grep -m1 clamd
31610 ?? 0:10.14 clamd
When I run clamscan it works and detects a known problem.
But, when I run clamdscan on the same
On 20.08.18 17:55, Michael Newman wrote:
clamd is running:
MrMuscle:~ mnewman$ ps -A | grep -m1 clamd
31610 ?? 0:10.14 clamd
When I run clamscan it works and detects a known problem.
But, when I run clamdscan on the same directory, it just instantly stops
without scanning.
What have
Check the logs and config files.
Clamscan loads the databases itself before running. It does not need clamd to
be running in order to work.
Clamdscan attempts to use a socket to talk with clamd for the scanning of
files. If there is an error, one of two things is happening:
Either the
Please post the results of the following Terminal Command:
sudo clamconf
-Al-
On Mon, Aug 20, 2018 at 03:55 AM, Michael Newman wrote:
> Mac 10.13.6
>
> clamd is running:
>
> MrMuscle:~ mnewman$ ps -A | grep -m1 clamd
> 31610 ?? 0:10.14 clamd
>
> When I run clamscan it works and
Mac 10.13.6
clamd is running:
MrMuscle:~ mnewman$ ps -A | grep -m1 clamd
31610 ?? 0:10.14 clamd
When I run clamscan it works and detects a known problem.
But, when I run clamdscan on the same directory, it just instantly stops
without scanning.
What have I done wrong?
MrMuscle:~
