From: Robert Klemme <shortcutter@...>
Date: 2009-11-13T01:12:53+09:00
Subject: Re: forking behaves differently when using apache

2009/11/12 Nick Brown <nick@nick-brown.com>:
> Elanor: I'm using the default apache2 config as distributed by Ubuntu
> 9.10. Is there a particular Apache directive I could use to make it
> behave the way I expect?
>
> Robert: Closing STDIN and STDOUT seemed to do the trick! Thanks. Just so
> I grok this: Apache, by default, will wait until all subprocesses close
> their IO streams before it sends a CGI program's output to the browser?

It seems so.  You'll probably have more luck with this question when
placed in an Apache forum.  Reading the docs might also help. ;-)

> Is that correct? Is there a better way to kick off such processes? Or is
> manually closing STDIN and STDOUT every time I fork the ideal solution?

Since I have no idea what your process does or is supposed to do I
cannot really tell.  You'll probably want to look into the features
available to daemonize a process, e.g

http://www.ruby-doc.org/core-1.9/classes/Process.html#M002265

Kind regards

robert


-- 
remember.guy do |as, often| as.you_can - without end
http://blog.rubybestpractices.com/