Been searching and performing trial and error for days and cannot find anything to resolve my attempts to establish clamd.scan.service on Fedora 16.

I've uncommented and configure scan.conf as prescibed, enabled the systemd service, and tried a myriad of other permissions based tips I've uncovered here and there, yet I still get:I have updated via freshclam and establishd it as a daemon and can perform clamscan without issue.

Am I thinking of clamd.scan.service correctly; will it run as a stand-alone on-access scan service or is simply available to complement some other tool or script to call it? My desire is to have this run as a true on-access scan daemon (set it and forget it) on a box acting as PDC with NIX and Windows members, the PDC is also an HTTP server.

Any insight on helping me 1) understand how I should think about the daemon and 2) minimum configuration to meet my intended use as stated above would be appreciated.

Cheers

Hi, it seems you have a wrong configuration.

The clamav default configuration is sufficient for many cases enough.

It depends what do you want to scan?

The daemon by default offers the scan service. It just means that the program (clamav) is loaded in the memory and when you call it, it scans file(s) or given data very quickly.

If you want to set on-access file scan, you have to use an additional software to invoke clamav. I do not know the direct way of using clamavd to scan.

Thanks for the reply, that for sure is helpful clarification of how the daemon works. I'll scrape everything and start over and see if I can troubleshoot in a more controlled fashion.

I can see that you edited the title adding "Closed" to it. You can mark the thread as solved instead (from the thread tools menu at the top of the screen)