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? That really doesn't seem all that > much like a win to me. I'd rather that the calling application was > allowed to make an immediate decision (defer this mail, etc) than get > stuck waiting waiting on a reply for an indeterminate amount of time.
How is this any different than any other time something connects to the socket and waits for a response, say when clamd is reloading it's database, or is under high load ? To me it's simply a consistant behavior. However I do think the other option of the parrent process not exiting until the socket is created is also a good idea, possibly better. Since this is the way clamav-milter works without the --external option it is also consistant. ========================================================== Chris Candreva -- [EMAIL PROTECTED] -- (914) 948-3162 WestNet Internet Services of Westchester http://www.westnet.com/ _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
