That sounds do-able, thanks for the hint
> The only thing I can't remember is how to tell each clamdscan which
> clamd to use, but I'm pretty sure it's possible.
as our application directly talks to clamd that will be easy to solve.
Think the overhead can be more reduced as the 2nd clamd instanc
Could you run two copies of clamd, one using stock db and the other using
your custom sigs? Then you would only need to signal the one running the
custom sigs when they change. Yes you would need to trigger two scans of
the target data, but the overhead shouldn't be too bad. The only thing I
can't
We have the problem that we change our custom clamav rules quite often.
A job syncs changed rules files to clamav server and then sends a
SIGUSR2 signal to reload the signatures. In that time of reloading
clamav does not really work and the application using clamd has to wait
for up to 30s.
So we w
