@Dysonco i share your frustration with the lack of support with the apps in truenas and i agree with you.
Supposedly everybody is using ClamAV in their system, and yet very few people chime in when it comes to answer questions about it.
ClamAv is kind of complicated and it took me lots of hours reading throught the manual to understand it. So, i will give you pointers and you should take it from there as i cannot possibly teach you everything i know about this app.
The way clamAV works is not how you think. It doesn't have a web interface or any other GUI. it is more like a command.
ClamAV is installed in a container, meaning that initially it doesn't have access to the system files.
So, the first thing you need to do is to add the system folder you want to scan, as a local folder inside the ClamAV container.
After you deploy the app, clamscan will be running but, how do you start a scan?
Well in a bare metal system, if you wanted to scan a directory called "scandir" then you would have to go to the terminal and type a command similar to :
clamscan -zri /scandir
That will get the scan going.
Then, to automate things, you would add a cronjob to run that command at a certain schedule of your choosing.
Most people (like me) create a script to run additional commands besides this. For instance, my script scans the folder and then sends me an email with the results. My cronjob runs it once a month.
Now, since ClamAV is not installed baremetal the process will be a bit different. ClamAV is installed in a container and you would have to pass the command from the main system to the container. For me this was the most difficult part to figure out but the people from heavscript have an example of a script that does just that. It can be found at
Command to Container Cron Job.
I used that example as basis for my script so it could issue the command from Truenas to the ClamAV container via a cronjob.
Now, that is MY setup. I believe the Truenas implementation of ClamAV has builtin functions to setup a cronjob for scans. Just enable the function
"Enable conjob" and set up a schedule for it. It should look similar to this:
If i were you, i would start there.
If you want more advanced functions such as emails reports, then i would study how to send a command to a container and use one of the many clamAV scripts available on the web.
Another reason why i like to run my own script is that i can use the command "clamdscan" which is much faster than "clamscan". To give you an idea, in my system a scan with "clamscan" takes about 5 days, the same scan takes about 40 minutes with "clamdscan". I don't remember the reason why but i believe "clamdscan" is a multicore process while "clamscan" is a single core one (I'm not sure about this so please do your research if interested in learning more).
As you can see, ClamAV is not as straight forward to setup. I think Truenas made a great effort in their implementation but without email reports the end user will never get feedback that the app is even running so it is very frustrating to use.
I hope this can get you going because you will never get a proper response from IXsystems about how their own implementation of Apps works.
