stas 02/04/13 12:26:54
Modified: src/docs/1.0/guide debug.pod strategy.pod
Log:
fix broken links
Revision Changes Path
1.8 +10 -8 modperl-docs/src/docs/1.0/guide/debug.pod
Index: debug.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/debug.pod,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- debug.pod 4 Apr 2002 02:24:27 -0000 1.7
+++ debug.pod 13 Apr 2002 19:26:54 -0000 1.8
@@ -276,7 +276,7 @@
of colored output for easier reading). You might need to ask your ISP
to install this script for general use. See L<Watching the error_log
file without telneting to the
-server|guide::snippets/Watching_the_error_log_File_With> .
+server|guide::snippets/Watching_the_error_log_File_Without_Telneting_to_the_Server>
.
=head2 The Importance of Warnings
@@ -1075,7 +1075,8 @@
=head1 Handling Server Timeout Cases and Working with $SIG{ALRM}
A similar situation to L<Pressed Stop button
-disease|guide::debug/Handling_the_User_pressed_Stop_> happens when the
+disease|guide::debug/Handling_the__User_pressed_Stop_button__case>
+happens when the
browser times out the connection (is it about 2 minutes?). There are
cases when your script is about to perform a very long operation and
there is a chance that its duration will be longer than the client's
@@ -1099,7 +1100,7 @@
(L<CVS version|guide::download/mod_perl>). As a matter of fact none of the
C<local $SIG{FOO}> signals restores the original C handler - read
L<Debugging Signal Handlers
-($SIG{FOO})|guide::debug/Debugging_Signal_Handlers_SIG_> for a debug
+($SIG{FOO})|guide::debug/Debugging_Signal_Handlers___SIG_FOO__> for a debug
technique and a possible workaround.
=head1 Looking inside the server
@@ -1334,7 +1335,7 @@
=head1 Sometimes My Script Works, Sometimes It Does Not
See L<Sometimes it Works Sometimes it does
-Not|guide::porting/Sometimes_it_Works_Sometimes_it>
+Not|guide::porting/Sometimes_it_Works__Sometimes_it_Doesn_t>
=head1 Code Debug
@@ -3023,8 +3024,9 @@
But if you have fifty processes, it can be quite hard to spot such a
process. L<Apache::Watchdog::RunAway is a hanging processes monitor
-and terminator|guide::modules/Apache_Watchdog_RunAway_Hang> that implements
-this feature and should be used to solve this kind of problem.
+and
terminator|guide::modules/Apache__Watchdog__RunAway___Hanging_Processes_Monitor_and_Terminator>
+that implements this feature and should be used to solve this kind of
+problem.
If you've got a real problem, and the processes hang one after the
other, the time will come when the number of hanging processes is
@@ -3034,7 +3036,7 @@
resolve it and notify the administrator using a simple crontab
watchdog that requests some very light script periodically. (See
L<Monitoring the Server. A
-watchdog.|guide::control/Monitoring_the_Server_A_watchdo>)
+watchdog.|guide::control/Monitoring_the_Server___A_watchdog_>)
In the watchdog you set a timeout appropriate for your service, which
may be anything from a few seconds to a few minutes. If the server
@@ -3917,7 +3919,7 @@
C<Apache::DebugInfo> offers the ability to monitor various bits of
per-request data. Its functionality is similar to
-L<Apache::DumpHeaders|guide::debug/Debugging_mod_perl_>
+L<Apache::DumpHeaders|guide::debug/Apache__DumpHeaders___Watch_HTTP_Transaction_Via_Headers>
while offering several additional features, including the ability to:
=over
1.5 +12 -10 modperl-docs/src/docs/1.0/guide/strategy.pod
Index: strategy.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/strategy.pod,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- strategy.pod 3 Apr 2002 09:16:08 -0000 1.4
+++ strategy.pod 13 Apr 2002 19:26:54 -0000 1.5
@@ -115,10 +115,11 @@
The DSO module (C<mod_so>) adds size and complexity to your binaries.
Refer to the section L<"Pros and Cons of Building mod_perl as
-DSO|guide::install/Pros_and_Cons_of_Building_mod_pe"> for more information.
+DSO|guide::install/Pros_and_Cons_of_Building_mod_perl_as_DSO">
+for more information.
Build details: L<Build mod_perl as DSO inside Apache source tree via
-APACI|guide::install/Build_mod_perl_as_a_DSO_inside_t>
+APACI|guide::install/Build_mod_perl_as_a_DSO_outside_the_Apache_Source_Tree_via_APXS>
=item 4
@@ -238,7 +239,8 @@
for you!
For implementation notes, see the "L<One Plain and One mod_perl
-enabled Apache Servers|guide::scenario/One_Plain_and_One_mod_perl_enabl>"
+enabled
+Apache
Servers|guide::scenario/One_Plain_and_One_mod_perl_enabled_Apache_Servers>"
section in the implementations chapter.
=head2 One Plain Apache and One mod_perl-enabled Apache Servers
@@ -297,8 +299,7 @@
need the attention of the heavy servers. This is not an issue if you
hide the internal port implementations, so the client sees only one
server running on port C<80>. (See L<Publishing Port Numbers other
-than
-80|guide::config/Publishing_Port_Numbers_other_th>)
+than 80|guide::config/Publishing_Port_Numbers_other_than_80>)
The disadvantages:
@@ -342,7 +343,8 @@
Before you go on with this solution you really want to look at the
L<Adding a Proxy Server in http Accelerator
-Mode|guide::strategy/Adding_a_Proxy_Server_in_http_Ac> section.
+Mode|guide::strategy/Adding_a_Proxy_Server_in_http_Accelerator_Mode>
+section.
For implementation notes see the "L<One Plain and One mod_perl enabled
Apache Servers|guide::scenario/One_Plain_and_One_mod_perl_enabl>" section in
@@ -682,10 +684,10 @@
For implementation details, see the sections L<Running One Webserver
and Squid in httpd Accelerator
-Mode|guide::scenario/Running_One_Webserver_and_Squid_> and L<Running Two
-Webservers and Squid in httpd Accelerator
-Mode|guide::scenario/Running_Two_webservers_and_Squid> in the implementations
-chapter.
+Mode|guide::scenario/Running_One_Webserver_and_Squid_in_httpd_Accelerator_Mode>
+and L<Running Two Webservers and Squid in httpd Accelerator
+Mode|guide::scenario/Running_Two_webservers_and_Squid_in_httpd_Accelerator_Mode>
+in the implementations chapter.
=head2 Apache's mod_proxy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
