Hi,
* Julius Plenz pl...@cis.fu-berlin.de [2014-04-07 20:43]:
1) Start reload_db() in a background thread, resume scanning, and call
back once the new engine is in place; then exchange the pointers
from old to new engine and free the old one.
FWIW, I have implemented this option,
Thanks for sending a patch, we will look at integrating it with ClamAV.
I have opened bug # 10979 at bugzilla.clamav.net for tracking.
On Mon, Apr 28, 2014 at 10:29 AM, Julius Plenz pl...@cis.fu-berlin.dewrote:
Hi,
* Julius Plenz pl...@cis.fu-berlin.de [2014-04-07 20:43]:
1) Start
Hi, Mark!
* Mark Pizzolato - ClamAV-devel clamav-de...@subscriptions.pizzolato.net
[2014-04-10 18:45]:
One more question (as I originally said, I haven't looked closely at
either the current code or your suggested patch)... What happens if
multiple reload requests come in right after each
Hi, Mark!
* Mark Pizzolato - ClamAV-devel clamav-de...@subscriptions.pizzolato.net
[2014-04-08 00:02]:
It appears that for every connection that is acceptey by clamd,
the current engine value is passed in the conn struct. The
engine struct has a ref count, and a process grabs the engine by
Hi Julius,
On Thursday, April 10, 2014 at 4:19 AM, Julius Plenz wrote:
Hi, Mark!
* Mark Pizzolato - ClamAV-devel clamav-de...@subscriptions.pizzolato.net
[2014-04-08 00:02]:
It appears that for every connection that is acceptey by clamd, the
current engine value is passed in the conn
Hi, Mark!
* Mark Pizzolato - ClamAV-devel clamav-de...@subscriptions.pizzolato.net
[2014-04-08 00:02]:
It appears that for every connection that is acceptey by clamd,
the current engine value is passed in the conn struct. The
engine struct has a ref count, and a process grabs the engine by
Hi,
1) Start reload_db() in a background thread, resume scanning, and call
back once the new engine is in place; then exchange the pointers
from old to new engine and free the old one.
FWIW, I have implemented this option, and it seems to work just fine.
Patch is pasted below.
Do you
1) Start reload_db() in a background thread, resume scanning, and call
back once the new engine is in place; then exchange the pointers
from old to new engine and free the old one.
FWIW, I have implemented this option, and it seems to work just fine.
Patch is pasted below.
Do
Hi, Mark!
* Mark Pizzolato - ClamAV-devel clamav-de...@subscriptions.pizzolato.net
[2014-04-07 21:17]:
I haven't looked closely, but how is the fact that each thread
(which may currently be scanning a different file and may finish at
some arbitrary time in the future) has a reference to the
Hi Julius,
On Monday, April 07, 2014 at 1:50 PM, Julius Plenz wrote:
* Mark Pizzolato - ClamAV-devel clamav-
de...@subscriptions.pizzolato.net [2014-04-07 21:17]:
I haven't looked closely, but how is the fact that each thread (which
may currently be scanning a different file and may finish
10 matches
Mail list logo
