;
> On Tue, Apr 30, 2019, 9:08 AM Tobi <mailto:jahli...@gmx.ch>> mailto:jahli...@gmx.ch>> wrote:
>
> 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 s
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
As far as I understand the release notes of 99.3 its a security fix which has
nothing to do with former 99.3 beta.
The former beta now is 0.100
(http://blog.clamav.net/2018/01/clamav-version-number-adjustment.html).
So at least for me it makes sense that you have to remove the beta first to
Do you mean this one ?
http://blog.clamav.net/2018/01/clamav-0993-has-been-released.html
Am 26. Januar 2018 14:03:14 MEZ schrieb Andreas Schulze
:
>
___
clamav-users mailing list
clamav-users@lists.clamav.net
My boxes in NL can still download
wget http://database.clamav.net/daily-23697.cdiff
HTTP request sent, awaiting response... 200 OK
dig database.clamav.net
database.clamav.net.43 IN CNAME db.local.clamav.net.
db.local.clamav.net.582 IN CNAME db.nl.clamav.net.
Hi Chris
sorry I was not clear enough. I did not mean to start the service via systemd
but to call like
sudo /usr/sbin/clamd -c /path/to/config
and see then if the socket has been created in expected location.
Cheers
tobi
- Originale Nachricht -
Von: Chris <cpoll...@embarqmail.
It might a systemd issue. Have you tried to start clamd by calling it directly
on cli? Does it create the socket then?
Cheers
tobi
- Originale Nachricht -
Von: Chris <cpoll...@embarqmail.com>
Gesendet: 07.08.16 - 04:49
An: clamav-users@lists.clamav.net
Betreff: [clamav-users]