Author: stas Date: Thu Dec 2 16:16:32 2004 New Revision: 109599 URL: http://svn.apache.org/viewcvs?view=rev&rev=109599 Log: fix pod
Modified: perl/modperl/docs/trunk/src/docs/2.0/user/handlers/server.pod Modified: perl/modperl/docs/trunk/src/docs/2.0/user/handlers/server.pod Url: http://svn.apache.org/viewcvs/perl/modperl/docs/trunk/src/docs/2.0/user/handlers/server.pod?view=diff&rev=109599&p1=perl/modperl/docs/trunk/src/docs/2.0/user/handlers/server.pod&r1=109598&p2=perl/modperl/docs/trunk/src/docs/2.0/user/handlers/server.pod&r2=109599 ============================================================================== --- perl/modperl/docs/trunk/src/docs/2.0/user/handlers/server.pod (original) +++ perl/modperl/docs/trunk/src/docs/2.0/user/handlers/server.pod Thu Dec 2 16:16:32 2004 @@ -303,7 +303,7 @@ -=head2 PerlPostConfigHandler +=head2 C<PerlPostConfigHandler> The I<post_config> phase happens right after Apache has processed the configuration files, before any child processes were spawned (which @@ -331,7 +331,7 @@ } As you can see, its arguments are identical to the -L<I<open_logs|/C_PerlOpenLogsHandler_>> phase's handler. In this +I<L<open_logs|/C_PerlOpenLogsHandler_>> phase's handler. In this example handler we don't do much, but logging that the configuration was completed and returning right away. @@ -356,7 +356,7 @@ -=head2 PerlChildInitHandler +=head2 C<PerlChildInitHandler> The I<child_init> phase happens immediately after the child process is spawned. Each child process (not a thread!) will run the hooks of this @@ -396,7 +396,7 @@ -=head2 PerlChildExitHandler +=head2 C<PerlChildExitHandler> Opposite to the I<child_init> phase, the I<child_exit> phase is executed before the child process exits. Notice that it happens only --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]