You are viewing a plain text version of this content. The canonical link for it is here.

Posted to bugs@httpd.apache.org by bu...@apache.org on 2005/02/21 14:44:21 UTC

DO NOT REPLY [Bug 33668] - (ANSI C) Cgi & fork

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=33668>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=33668


trawick@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




------- Additional Comments From trawick@apache.org  2005-02-21 14:44 -------
In the case where you are running as a CGI, the puts() operation leaves the text
in the buffer for stdout, and when the fork() occurs the buffer is copied too.

In the case where you are running from the command-line, stdout is buffered
differently (either no buffering or buffered until end of line -- I can't
remember), so the text has already been flushed prior to fork(), so the new
child processes have nothing in their stdout buffer when they start running.

This is a generic C/Unix programming issue, and nothing to do with Apache.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org