DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18975>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18975 CustomLog piped program ends unexpectedily ------- Additional Comments From [EMAIL PROTECTED] 2003-04-16 10:26 ------- The last part of the strace is as follows: read(255, "\t\t\t\t\t\t\nexit 0\n", 1347) = 14 rt_sigprocmask(SIG_BLOCK, NULL, [RT_0], 8) = 0 rt_sigprocmask(SIG_BLOCK, [CHLD TTOU], [RT_0], 8) = 0 rt_sigprocmask(SIG_SETMASK, [RT_0], NULL, 8) = 0 rt_sigprocmask(SIG_BLOCK, [CHLD], [RT_0], 8) = 0 rt_sigprocmask(SIG_SETMASK, [RT_0], NULL, 8) = 0 rt_sigprocmask(SIG_SETMASK, [RT_0], NULL, 8) = 0 _exit(0) = ? Look at the first line quoted above: It looks to me like the shell is reading "exit 0" from your piped log script and then exiting. So your piped log script is choosing to exit. I don't have any great guesses why, but I see read(255, "\nif echo $INPUT |grep -f $ANPATH"..., 1347) = 391 a bit above, followed by running some child processes... maybe you don't see the expected data in the input and choose to exit? I don't see Apache doing anything weird (your script didn't hit EOF on stdin, your script didn't get SIGTERM from Apache, etc.). You'll need to review your script or add some tracing to it to see why your script is choosing to exit. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
