J.R. is correct about the `--database=FILE/DIR` or  `-d FILE/DIR` option being for clamscan.  The for clamd, you'll have to place it in your database directory.

Our documentation on Github is moving from the clamav-devel repo over to our https://github.com/Cisco-Talos/clamav-faq repository so it can be rendered on clamav.net.
If you feel like there are mistakes or deficiencies in the documentation, we're very responsive to pull requests on https://github.com/Cisco-Talos/clamav-faq.  Please note that links between pages must use absolute links to the clamav.net URLs for now, as the markdown rendering code in our website currently doesn't handle nested directories very well.

Here's the link for our signature writing docs on clamav.net:
https://www.clamav.net/documents/creating-signatures-for-clamav 

This page also has a few helpful tips:
https://www.clamav.net/documents/signature-testing-and-management 
 
If you plan to work regularly on ClamAV signatures, and especially if you'd like to submit them to our malware research team for inclusion in the official database, you may wish to join the community-sigs mailing list.

Regards,
Micah
 
Micah Snyder
ClamAV Development
Talos
Cisco Systems, Inc.


On Jan 30, 2019, at 10:40 AM, J.R. <themadbeaker@gmail.com> wrote:

Also I believe you have to use clamscan, not clamdscan if you want to
use the "-d" option. However once you test it successfully you can add
it as a custom db for clamd to load.
_______________________________________________
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml