On Thursday 13 December 2001 11:02 am, Allan Edwards wrote:
> This might also be a problem on unix but I haven't tested.
> When cgi's are launched a window sometimes pops up, same for
> mod_include "exec cgi". Is there a reason we are not
> launching the cgi as a detached process?
You definately
From: "Allan Edwards" <[EMAIL PROTECTED]>
Sent: Thursday, December 13, 2001 1:02 PM
> This might also be a problem on unix but I haven't tested.
> When cgi's are launched a window sometimes pops up, same for
> mod_include "exec cgi". Is there a reason we are not
> launching the cgi as a detache
Ryan Bloom <[EMAIL PROTECTED]> writes:
> On Thursday 13 December 2001 11:02 am, Allan Edwards wrote:
> > This might also be a problem on unix but I haven't tested.
> > When cgi's are launched a window sometimes pops up, same for
> > mod_include "exec cgi". Is there a reason we are not
> > launchi
> > mod_include "exec cgi". Is there a reason we are not
> > launching the cgi as a detached process?
>
> Yes. They are broken for all 16 bit CGIs.
16 bit CGI's seem to be broken at the moment anyway.
> We need some mechansim to
> pass off the fact that we've tested, and it is a good, well b
From: "Ryan Bloom" <[EMAIL PROTECTED]>
Sent: Thursday, December 13, 2001 1:09 PM
> On Thursday 13 December 2001 11:02 am, Allan Edwards wrote:
> > This might also be a problem on unix but I haven't tested.
> > When cgi's are launched a window sometimes pops up, same for
> > mod_include "exec cgi
From: "Jeff Trawick" <[EMAIL PROTECTED]>
Sent: Thursday, December 13, 2001 1:17 PM
> what if we had a long-running-daemon attribute and a non-interactive
> attribute (yeah, please come up with better names):
>
> long-running-daemonnon-interactive
>
> Win32
