ClamAV Configuration Templates
Locate and customize clamav configuration templates using the current Jinja renderer and supported global override path.
The ClamAV builder renders the daemon configuration from antivirus settings when the service is installed.
Locations and selection
| Type | Location |
|---|---|
| Shipped default | /usr/local/eenos/templates/clamav/clamd.conf.jinja |
| Global custom override | /usr/local/eenos/templates/clamav/custom/clamd.conf.jinja |
The reviewed caller checks the matching custom file before its default. It does not implement an account-specific override for this component. Use the Jinja syntax and data expected by that caller, regardless of the filename extension.
The reviewed builder writes /etc/clamav/clamd.conf.
Customize and validate
Copy the current compatible default into the supported custom location, edit the copy and retain the prior version. Do not modify the shipped template or only edit an automatically generated destination file: a later rebuild can replace it.
Keep socket, ownership, scan limits and required service paths compatible with the installed ClamAV package. Test access and scanning behavior in staging before applying a managed rebuild. A template alone does not install or enable ClamAV.
Review the rendered output in staging and the component's native validation result. Template rendering alone does not prove usable service configuration. Apply a planned rebuild/reload only after review, and keep a working template/output pair for rollback.
After updates, compare your override with the new shipped default and merge required changes. See the panel administration guide and template rollout guidance.