stas 2002/07/31 07:44:20
Modified: src/docs/1.0/guide Changes.pod config.pod debug.pod
frequent.pod getwet.pod performance.pod porting.pod
scenario.pod snippets.pod troubleshooting.pod
Log:
sync the internal links to the files that have moved
Revision Changes Path
1.31 +1 -1 modperl-docs/src/docs/1.0/guide/Changes.pod
Index: Changes.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/Changes.pod,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -r1.30 -r1.31
--- Changes.pod 16 Jul 2002 06:43:42 -0000 1.30
+++ Changes.pod 31 Jul 2002 14:44:19 -0000 1.31
@@ -142,7 +142,7 @@
* Minor corrections:
- o remove qw() or variables list in general::perl_reference (Tim Noll
+ o remove qw() or variables list in general::perl_reference::perl_reference
(Tim Noll
<[EMAIL PROTECTED]>)
o install: (Per Einar Ellefsen <[EMAIL PROTECTED]>, Karl Olson
1.13 +1 -1 modperl-docs/src/docs/1.0/guide/config.pod
Index: config.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/config.pod,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- config.pod 29 May 2002 05:13:57 -0000 1.12
+++ config.pod 31 Jul 2002 14:44:19 -0000 1.13
@@ -1505,7 +1505,7 @@
the startup file and in the script itself. The confusion arises due to
misunderstanding the C<use()> function. C<use()> normally performs two
operations, namely C<require()> and C<import()>, called within a
-C<BEGIN> block. See the section "L<use()|general::perl_reference/use__>" for
a detailed
+C<BEGIN> block. See the section
"L<use()|general::perl_reference::perl_reference/use__>" for a detailed
explanation of the use(), require() and import() functions.
In the startup file we don't want to import any symbols since they
1.12 +1 -1 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.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- debug.pod 31 Jul 2002 13:05:35 -0000 1.11
+++ debug.pod 31 Jul 2002 14:44:19 -0000 1.12
@@ -3037,7 +3037,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.|general::control/Monitoring_the_Server___A_watchdog_>)
+watchdog.|general::control::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
1.7 +1 -1 modperl-docs/src/docs/1.0/guide/frequent.pod
Index: frequent.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/frequent.pod,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- frequent.pod 12 May 2002 18:09:12 -0000 1.6
+++ frequent.pod 31 Jul 2002 14:44:19 -0000 1.7
@@ -12,7 +12,7 @@
=head1 my() scoped variable in nested subroutines
See the section "L<my() Scoped Variable in Nested
-Subroutines|general::perl_reference/my___Scoped_Variable_in_Nested_Subroutines>".
+Subroutines|general::perl_reference::perl_reference/my___Scoped_Variable_in_Nested_Subroutines>".
=head1 Segfaults caused by PerlFreshRestart
1.7 +1 -1 modperl-docs/src/docs/1.0/guide/getwet.pod
Index: getwet.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/getwet.pod,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- getwet.pod 14 May 2002 10:20:58 -0000 1.6
+++ getwet.pod 31 Jul 2002 14:44:19 -0000 1.7
@@ -838,7 +838,7 @@
new scripts may need to be added, old ones removed, and the server
software will need upgrades and security fixes. And if the server goes
down, fast recovery is essential. These issues are considered in
-the L<Controlling your server chapter|docs::general::control>.
+the L<Controlling your server chapter|docs::general::control::control>.
Finally, the most important aspect of mod_perl is the Apache Perl API,
which allows intervention at any or every stage of request
1.21 +3 -3 modperl-docs/src/docs/1.0/guide/performance.pod
Index: performance.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/performance.pod,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- performance.pod 30 Jul 2002 06:04:15 -0000 1.20
+++ performance.pod 31 Jul 2002 14:44:19 -0000 1.21
@@ -77,7 +77,7 @@
=head2 Software Requirements
Covered in the section "L<Choosing an Operating
-System|general::hardware/Choosing_an_Operating_System>".
+System|general::hardware::hardware/Choosing_an_Operating_System>".
=head2 Hardware Requirements
@@ -134,7 +134,7 @@
but exponentially!
More coverage is provided in the section "L<Choosing
-Hardware|general::hardware/Choosing_Hardware>".
+Hardware|general::hardware::hardware/Choosing_Hardware>".
=head1 Essential Tools
@@ -4758,7 +4758,7 @@
processes would show only one entry or none at all, since they might
not serve the same requests as the others. For more hints see the
section "L<Run the server in single
-mode|general::control/Running_a_Server_in_Single_Process_Mode>".
+mode|general::control::control/Running_a_Server_in_Single_Process_Mode>".
=head1 Improving Performance by Prevention
1.13 +14 -14 modperl-docs/src/docs/1.0/guide/porting.pod
Index: porting.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/porting.pod,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- porting.pod 16 Jul 2002 06:43:42 -0000 1.12
+++ porting.pod 31 Jul 2002 14:44:19 -0000 1.13
@@ -40,7 +40,7 @@
practices, since mod_perl doesn't tolerate sloppy programming.
This chapter relies on a certain level of Perl knowledge. Please
-read through the L<Perl Reference|general::perl_reference/Perl_Reference_>
chapter and make sure you
+read through the L<Perl
Reference|general::perl_reference::perl_reference/Perl_Reference_> chapter and
make sure you
know the material covered there. This will allow me to concentrate on
pure mod_perl issues and make them more prominent to the experienced
Perl programmer, which would otherwise be lost in the sea of Perl
@@ -136,7 +136,7 @@
opposed to anonymous - subroutine defined inside another subroutine)
that refers to a lexically scoped variable defined outside this nested
subroutine. This effect is explained in L<my() Scoped Variable in
-Nested Subroutines|general::perl_reference/my_Scoped_Variable_in_Nested_S>.
+Nested
Subroutines|general::perl_reference::perl_reference/my_Scoped_Variable_in_Nested_S>.
Do you see a nested named subroutine in my script? I don't! What's
going on? Maybe it's a bug? But wait, maybe the perl interpreter sees
@@ -274,7 +274,7 @@
(unless I create them myself :).
The section 'L<Remedies for Inner
-Subroutines|general::perl_reference/Remedies_for_Inner_Subroutines>'
discusses
+Subroutines|general::perl_reference::perl_reference/Remedies_for_Inner_Subroutines>'
discusses
many other possible workarounds for this problem.
You shouldn't be intimidated by this issue at all, since Perl is your
@@ -358,7 +358,7 @@
Of course none of the warnings will be reported if the warning
mechanism is not turned C<On>. Refer to the section "L<Tracing
-Warnings Reports|general::perl_reference/Tracing_Warnings_Reports>" to learn
about
+Warnings
Reports|general::perl_reference::perl_reference/Tracing_Warnings_Reports>" to
learn about
warnings in general and to the "L<Warnings|guide::porting/Warnings>" section
to learn how to turn them on and off under mod_perl.
@@ -483,10 +483,10 @@
}
To make sure you don't miss these bugs always test your CGI in
-L<single process
mode|general::control/Running_a_Server_in_Single_Process_Mode>.
+L<single process
mode|general::control::control/Running_a_Server_in_Single_Process_Mode>.
To solve this particular C</o> modifier problem refer to L<Compiled
-Regular Expressions|general::perl_reference/Compiled_Regular_Expressions>.
+Regular
Expressions|general::perl_reference::perl_reference/Compiled_Regular_Expressions>.
=head1 Script's name space
@@ -498,7 +498,7 @@
=head1 @INC and mod_perl
The basic Perl C<@INC> behaviour is explained in section L<use(), require(),
-do(), %INC and @INC
Explained|general::perl_reference/use_require_do_INC_and>.
+do(), %INC and @INC
Explained|general::perl_reference::perl_reference/use_require_do_INC_and>.
When running under mod_perl, once the server is up C<@INC> is frozen
and cannot be updated. The only opportunity to I<temporarily> modify
@@ -541,7 +541,7 @@
=head1 Reloading Modules and Required Files
You might want to read the "L<use(), require(), do(), %INC and @INC
-Explained|general::perl_reference/use_require_do_INC_and>" before you
proceed with this
+Explained|general::perl_reference::perl_reference/use_require_do_INC_and>"
before you proceed with this
section.
When you develop plain CGI scripts, you can just change the code, and
@@ -571,7 +571,7 @@
The simplest approach is to restart the server each time you apply
some change to your code. See L<Server Restarting
-techniques|general::control/Restarting_Techniques>.
+techniques|general::control::control/Restarting_Techniques>.
After restarting the server about 100 times, you will tire of it and
you will look for other solutions.
@@ -1568,7 +1568,7 @@
=head1 Name collisions with Modules and libs
This section requires an in-depth understanding of L<use(), require(),
-do(), %INC and @INC |general::perl_reference/use_require_do_INC_and>.
+do(), %INC and @INC
|general::perl_reference::perl_reference/use_require_do_INC_and>.
To make things clear before we go into details: each child process has
its own C<%INC> hash which is used to store information about its
@@ -1694,7 +1694,7 @@
about C<Foo>. When you call the second script it will not know about
C<Foo> at all--it's like you've forgotten to write C<use Foo;>. Run
the server in L<single server
-mode|general::control/Running_a_Server_in_Single_Proce> to detect this kind
of
+mode|general::control::control/Running_a_Server_in_Single_Proce> to detect
this kind of
bug immediately.
You will see the following in the error_log file:
@@ -2236,7 +2236,7 @@
from request to request. This means that you must never rely on the
value of the global variable if it wasn't initialized at the beginning
of the request processing. See "L<Variables globally, lexically scoped
-and fully
qualified|general::perl_reference/Variables_Globally_Lexically_Sc>" for more
+and fully
qualified|general::perl_reference::perl_reference/Variables_Globally_Lexically_Sc>"
for more
info.
You should avoid using global variables unless it's impossible without
@@ -2245,7 +2245,7 @@
they are used. Use my() scoped variables wherever you can.
You should be especially careful with L<Perl Special
-Variables|general::perl_reference/The_Scope_of_the_Special_Perl_Va> which
cannot be
+Variables|general::perl_reference::perl_reference/The_Scope_of_the_Special_Perl_Va>
which cannot be
lexically scoped. You have to use local() instead.
=head1 Generating correct HTTP Headers
@@ -2565,7 +2565,7 @@
additional headers, such as cookies.
See also L<Correct Headers--A quick guide for mod_perl
-users|general::correct_headers/>
+users|general::correct_headers::correct_headers/>
=head1 NPH (Non Parsed Headers) scripts
1.9 +2 -2 modperl-docs/src/docs/1.0/guide/scenario.pod
Index: scenario.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/scenario.pod,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- scenario.pod 11 May 2002 11:54:44 -0000 1.8
+++ scenario.pod 31 Jul 2002 14:44:19 -0000 1.9
@@ -704,7 +704,7 @@
But this is only possible if you set the headers correctly. Refer to
the chapter L<Correct Headers - A quick guide for mod_perl
-users|general::correct_headers/> to learn more about generating the proper
+users|general::correct_headers::correct_headers/> to learn more about
generating the proper
caching headers under mod_perl. In case where only the scripts under
I</perl/caching-unfriendly> are not I<caching friendly> fix the above
setting to be:
@@ -715,7 +715,7 @@
But if you are lazy, or just have too many things to deal with, you
can leave the above directives the way we described. Just keep in
mind that one day you will want to reread this section and L<the
-headers generation tutorial|general::correct_headers/> to squeeze even more
+headers generation tutorial|general::correct_headers::correct_headers/> to
squeeze even more
power from your servers without investing money in more memory and
better hardware.
1.11 +1 -1 modperl-docs/src/docs/1.0/guide/snippets.pod
Index: snippets.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/snippets.pod,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- snippets.pod 15 May 2002 15:33:15 -0000 1.10
+++ snippets.pod 31 Jul 2002 14:44:19 -0000 1.11
@@ -123,7 +123,7 @@
information to the client instead of to I<error_log> you have to take
the responsibility yourself, by writing your own exception handler to
implement this behaviour. See the section "L<Exception Handling for
-mod_perl|general::perl_reference/Exception_Handling_for_mod_perl>" for more
information.
+mod_perl|general::perl_reference::perl_reference/Exception_Handling_for_mod_perl>"
for more information.
The code examples below can be useful with your own exception handlers
as well as with the default handlers.
1.13 +6 -6 modperl-docs/src/docs/1.0/guide/troubleshooting.pod
Index: troubleshooting.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/troubleshooting.pod,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- troubleshooting.pod 27 Jun 2002 16:05:21 -0000 1.12
+++ troubleshooting.pod 31 Jul 2002 14:44:19 -0000 1.13
@@ -153,12 +153,12 @@
=head2 Value of $x will not stay shared at - line 5
L<my() Scoped Variable in Nested
-Subroutines|general::perl_reference/my___Scoped_Variable_in_Nested_Subroutines>.
+Subroutines|general::perl_reference::perl_reference/my___Scoped_Variable_in_Nested_Subroutines>.
=head2 Value of $x may be unavailable at - line 5.
L<my() Scoped Variable in Nested
-Subroutines|general::perl_reference/my___Scoped_Variable_in_Nested_Subroutines>.
+Subroutines|general::perl_reference::perl_reference/my___Scoped_Variable_in_Nested_Subroutines>.
=head2 Can't locate loadable object for module XXX
@@ -246,8 +246,8 @@
=head2 Preventing mod_perl Processes From Going Wild
See the sections "L<Non-Scheduled Emergency Log
-Rotation|general::control/Non_Scheduled_Emergency_Log_Rotation>" and "L<All
RAM
-Consumed|general::control/All_RAM_Consumed>"
+Rotation|general::control::control/Non_Scheduled_Emergency_Log_Rotation>"
and "L<All RAM
+Consumed|general::control::control/All_RAM_Consumed>"
=head2 Segfaults when using XML::Parser
@@ -595,13 +595,13 @@
cleanup normally isn't a requirement, you can disable it by setting
the PERL_DESTRUCT_LEVEL environment variable to -1. See the section
"L<Speeding up the Apache Termination and
-Restart|general::control/Speeding_up_the_Apache_Termination_and_Restart>"
for
+Restart|general::control::control/Speeding_up_the_Apache_Termination_and_Restart>"
for
more information.
=head2 httpd keeps on growing after each restart
See the I<HUP Signal> explanation at the section:
-L<Server Stopping and
Restarting|general::control/Server_Stopping_and_Restarting>
+L<Server Stopping and
Restarting|general::control::control/Server_Stopping_and_Restarting>
=head1 Windows OS specific notes
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
