At 12:00 PM 6/22/2004, Brad Nicholes wrote: >>What if the default in APR is to run in a separate address space*, and >in >>places in Apache where on NetWare the child process should run in the >same >>address space there is a call to the proper procattr manipulator to >override >>the default so that the child runs in the same address space? (and >ignore any >>APR_ENOTIMPL retcode from that procattr manipulator so that no ifdef >NETWARE is >>needed around the call) > > The is actually the behavior that we don't want on NetWare. Running >CGI's or utilities like RotateLogs in a separate address space is very >painful and requires overhead and a performance hit that we don't want. >On NetWare we need to default to the current address space. BTW, an >address space on NetWare is, for the most part, very different than on >other platforms. 90% of what is running on the box, is running in the >same address space. > When we implemented the CGIMapExtension directive to associate a CGI >extension with an executible (NetWare doesn't have a shell like BASH to >handle the associations) there is an optional parameter called "detach" >which allows the user to specify wheither the associated executible >should be run in the current address space or a separate address space. >The default is the current address space.
Can I ask the obvious, then? When would a separate address space be desirable for an apr-based app to invoke a child/forked process?
