Re: [Clamav-users] Re: first impressions on 0.90

2007-02-16 Thread Tomasz Kojm
On Fri, 16 Feb 2007 15:28:18 + Ian Abbott <[EMAIL PROTECTED]> wrote: > My proposal is to change the order from: > > * fork (daemonize) > * load database > * open sockets > > to: > > * load database > * open sockets > * fork (daemonize) This won't work. In hardware accelerated m

Re: [Clamav-users] Re: first impressions on 0.90

2007-02-16 Thread Christopher X. Candreva
On Fri, 16 Feb 2007, Stephen Gran wrote: > > It would be something for other programs to connect to and wait for a > > response, instead of generating a "socket does not exist" error. > > So that they could potentially wait around until their internal timeout, > instead of immediately returning?

Re: [Clamav-users] Re: first impressions on 0.90

2007-02-16 Thread Stephen Gran
On Fri, Feb 16, 2007 at 10:17:18AM -0500, Christopher X. Candreva said: > On Fri, 16 Feb 2007, Stephen Gran wrote: > > > What would be the point of having a socket ready before clamd is > > ready to do any work? Maybe I'm missing something. > > It would be something for other programs to connect

Re: [Clamav-users] Re: first impressions on 0.90

2007-02-16 Thread Stephen Gran
On Fri, Feb 16, 2007 at 03:28:18PM +, Ian Abbott said: > On 16/02/2007 15:14, Stephen Gran wrote: > >What would be the point of having a socket ready before clamd is ready > >to do any work? Maybe I'm missing something. > > My proposal is to change the order from: > > * fork (daemonize) >

[Clamav-users] Re: first impressions on 0.90

2007-02-16 Thread Ian Abbott
On 16/02/2007 15:14, Stephen Gran wrote: On Fri, Feb 16, 2007 at 03:04:42PM +, Ian Abbott said: On 16/02/2007 13:51, James Kosin wrote: Ian Abbott wrote: On 14/02/2007 20:09, Rick Pim wrote: it's true; if i start clamd and then check, the clamd socket isn't there. but if i leave clamd

Re: [Clamav-users] Re: first impressions on 0.90

2007-02-16 Thread Christopher X. Candreva
On Fri, 16 Feb 2007, Stephen Gran wrote: > What would be the point of having a socket ready before clamd is ready > to do any work? Maybe I'm missing something. It would be something for other programs to connect to and wait for a response, instead of generating a "socket does not exist" error.

Re: [Clamav-users] Re: first impressions on 0.90

2007-02-16 Thread Stephen Gran
On Fri, Feb 16, 2007 at 03:04:42PM +, Ian Abbott said: > On 16/02/2007 13:51, James Kosin wrote: > >Ian Abbott wrote: > >>On 14/02/2007 20:09, Rick Pim wrote: > >>> it's true; if i start clamd and then check, the clamd socket isn't > >>> there. but if i leave clamd alone for a few seconds t

[Clamav-users] Re: first impressions on 0.90

2007-02-16 Thread Ian Abbott
On 16/02/2007 13:51, James Kosin wrote: Ian Abbott wrote: On 14/02/2007 20:09, Rick Pim wrote: it's true; if i start clamd and then check, the clamd socket isn't there. but if i leave clamd alone for a few seconds the socket appears and clamav-milter starts happily after that. i've tuc

Re: [Clamav-users] Re: first impressions on 0.90

2007-02-16 Thread James Kosin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ian Abbott wrote: > On 14/02/2007 20:09, Rick Pim wrote: >>it's true; if i start clamd and then check, the clamd socket isn't >>there. but if i leave clamd alone for a few seconds the socket >>appears and clamav-milter starts happily after

[Clamav-users] Re: first impressions on 0.90

2007-02-16 Thread Ian Abbott
On 14/02/2007 20:09, Rick Pim wrote: it's true; if i start clamd and then check, the clamd socket isn't there. but if i leave clamd alone for a few seconds the socket appears and clamav-milter starts happily after that. i've tucked a "sleep 30" into the startup script and things see