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 2006/02/09 17:37:02 UTC
DO NOT REPLY [Bug 16761] - CustomLog with pipe spawns process during config
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=16761>.
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=16761
------- Additional Comments From KGolomb@TradeCard.com 2006-02-09 17:37 -------
Created an attachment (id=17630)
--> (http://issues.apache.org/bugzilla/attachment.cgi?id=17630&action=view)
Patch to fix Hanging pipe logger processes.
It looks like on Win32 of log.c the piped log always starts the piped process
thru a cmd.exe shell. Which seems to be the root of this hanging piped
CustomLog / ErrorLog.
Changing the process creation from:
apr_procattr_cmdtype_set(procattr, APR_SHELLCMD_ENV)
to:
apr_procattr_cmdtype_set(procattr, APR_PROGRAM_ENV)
Will cause it to act the way it used and make it worrk correctly.
CMD.exe will then only be utilize for .cmd and .bat loggers where it is
necessary.
--
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