Let's suppose that the ClamD engine needs some time to reload the signatures, for example...
Wed Oct 28 10:23:27 2009 -> Reading databases from C:\ASSP\clamAV\data Wed Oct 28 10:24:26 2009 -> Database correctly reloaded (896020 signatures) now... during the reload, the scanner won't be answering to commands/scans (so probably the "ping" won't work either but get "stuck" wating for an anwer which will only come after clamd completes the reload) My question is... would ASSP in such a case get "stuck" in turn and/or (in the case of v2) declare the workers dead and, after firing up a "can't pass ... to any worker" decide to commit suicide and restart ? I know this isn't directly an ASSP issue, but I'm wondering if there may be some workaround to the above situation ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
