Sure, If you have a perl script as such:
#!/usr/local/bin/perl # # Do something bad require 'doesnt-exist'; Then reference this perl script in a customlog line: Eg. CustomLog "| /usr/bin/myperl.pl" "%h" Apache normally starts ONE copy of the perl script. However because this perl script bombs out, it keeps trying to restart the perl script (everytime it tries to log a hit as defined in the CustomLog). Eventually we had the maximum number of apache processes running and apache stopped responding to any requests. Steve On 18 Dec 1998 [EMAIL PROTECTED] wrote: > [In order for any reply to be added to the PR database, ] > [you need to include <[EMAIL PROTECTED]> in the Cc line ] > [and leave the subject line UNCHANGED. This is not done] > [automatically because of the potential for mail loops. ] > [If you do not include this Cc, your reply may be ig- ] > [nored unless you are responding to an explicit request ] > [from a developer. ] > [Reply only with text; DO NOT SEND ATTACHMENTS! ] > > > Synopsis: Logging To A File Freezes Apache > > State-Changed-From-To: open-feedback > State-Changed-By: marc > State-Changed-When: Fri Dec 18 10:45:56 PST 1998 > State-Changed-Why: > What do you mean by "does not work properly"? Please give > an example logging script that can be used to reproduce this. > >
