stas 02/05/11 04:54:45 Modified: src config.cfg src/docs/1.0/api Apache.pod src/docs/1.0/guide Changes.pod config.pod debug.pod frequent.pod help.pod install.pod intro.pod modules.pod performance.pod porting.pod scenario.pod snippets.pod strategy.pod troubleshooting.pod src/docs/general correct_headers.pod hardware.pod multiuser.pod perl_reference.pod src/maillist email-etiquette.pod src/products app-server.pod src/start/tips registry.pod Added: src/docs/tutorials .cvsignore Log: fix links after the files were moved around Revision Changes Path 1.26 +1 -0 modperl-docs/src/config.cfg Index: config.cfg =================================================================== RCS file: /home/cvs/modperl-docs/src/config.cfg,v retrieving revision 1.25 retrieving revision 1.26 diff -u -r1.25 -r1.26 --- config.cfg 10 May 2002 08:03:43 -0000 1.25 +++ config.cfg 11 May 2002 11:54:44 -0000 1.26 @@ -88,6 +88,7 @@ docs/2.0 docs/1.0/api docs/1.0 + docs . )], # what extensions to search for 1.9 +1 -1 modperl-docs/src/docs/1.0/api/Apache.pod Index: Apache.pod =================================================================== RCS file: /home/cvs/modperl-docs/src/docs/1.0/api/Apache.pod,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- Apache.pod 27 Apr 2002 03:34:13 -0000 1.8 +++ Apache.pod 11 May 2002 11:54:44 -0000 1.9 @@ -1029,7 +1029,7 @@ perl, L<Apache::Constants>, L<Apache::Registry>, -L<Apache::Debug>, +C<Apache::Debug>, L<Apache::Options>, CGI 1.20 +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.19 retrieving revision 1.20 diff -u -r1.19 -r1.20 --- Changes.pod 10 May 2002 07:47:40 -0000 1.19 +++ Changes.pod 11 May 2002 11:54:44 -0000 1.20 @@ -112,7 +112,7 @@ * Minor corrections: - o remove qw() or variables list in guide::perl (Tim Noll + o remove qw() or variables list in general::perl_reference (Tim Noll <[EMAIL PROTECTED]>) o install: (Per Einar Ellefsen <[EMAIL PROTECTED]>, Karl Olson 1.8 +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.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- config.pod 5 May 2002 18:22:33 -0000 1.7 +++ config.pod 11 May 2002 11:54:44 -0000 1.8 @@ -1402,7 +1402,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()|guide::perl/use__>" for a detailed +C<BEGIN> block. See the section "L<use()|general::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.9 +4 -4 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.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- debug.pod 13 Apr 2002 19:26:54 -0000 1.8 +++ debug.pod 11 May 2002 11:54:44 -0000 1.9 @@ -1097,7 +1097,7 @@ It was recently discovered that C<local $SIG{'ALRM'}> does not restore the original underlying C handler. This was fixed in mod_perl 1.19_01 -(L<CVS version|guide::download/mod_perl>). As a matter of fact none of the +(L<CVS version|download::third_party/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_FOO__> for a debug @@ -3036,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_watchdog_>) +watchdog.|general::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 @@ -3641,7 +3641,7 @@ C<Sys::Signal> module, which solves the problem: C<Sys::Signal> - Set signal handlers with restoration of the existing -C sighandler. Get it from L<CPAN|guide::download/Perl>. +C sighandler. Get it from L<CPAN|download::third_party/Perl>. The usage is simple. If the original code was: @@ -3913,7 +3913,7 @@ For more information read the module's manpage. -Download the module from L<CPAN|guide::download/CPAN_Downloads>. +Download the module from L<CPAN|download::third_party/CPAN_Downloads>. =head1 Apache::DebugInfo - Log Various Bits Of Per-Request Data 1.5 +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.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- frequent.pod 20 Mar 2002 17:43:04 -0000 1.4 +++ frequent.pod 11 May 2002 11:54:44 -0000 1.5 @@ -12,7 +12,7 @@ =head1 my() scoped variable in nested subroutines See the section "L<my() Scoped Variable in Nested -Subroutines|guide::perl/my___Scoped_Variable_in_Nested_Subroutines>". +Subroutines|general::perl_reference/my___Scoped_Variable_in_Nested_Subroutines>". =head1 Segfaults caused by PerlFreshRestart 1.17 +18 -18 modperl-docs/src/docs/1.0/guide/help.pod Index: help.pod =================================================================== RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/help.pod,v retrieving revision 1.16 retrieving revision 1.17 diff -u -r1.16 -r1.17 --- help.pod 10 May 2002 07:47:40 -0000 1.16 +++ help.pod 11 May 2002 11:54:44 -0000 1.17 @@ -10,23 +10,24 @@ =head1 READ ME FIRST -If, after reading this guide and the L<other documents|docs::general::offsite> -listed on this -site, you still don't have the answers/information needed, please -ask for help on the L<mod_perl users mailing list|maillist::list-modperl>. -But please, first try to browse the -L<mailing list archive|maillist::list-modperl/Searchable_Archives>. -Most of the time you will -find the answer to your questions by searching the archive, since it is -very likely that someone else has already encountered the same problem -and found a solution for it. If you ignore this advice, you should not -be surprised if your question is left unanswered - it bores people to -answer the same question more than once. This does not mean that you -should avoid asking questions, but you should not abuse the available -help and you should I<RTFM> before you call for I<HELP>. (Remember the -fable of the shepherd boy and the wolves). +If, after reading this guide, the L<general docs|docs::general::index> +and the L<other documents|docs::offsite::index> listed on this site, +you still don't have the answers/information needed, please ask for +help on the L<mod_perl users mailing list|maillist::list-modperl>. +But please, first try to browse the L<mailing list +archive|maillist::list-modperl/Searchable_Archives>. Most of the time +you will find the answer to your questions by searching the archive, +since it is very likely that someone else has already encountered the +same problem and found a solution for it. If you ignore this advice, +you should not be surprised if your question is left unanswered - it +bores people to answer the same question more than once. This does +not mean that you should avoid asking questions, but you should not +abuse the available help and you should I<RTFM> before you call for +I<HELP>. (Remember the fable of the shepherd boy and the wolves). -Another possibilty is to look in the general L<Getting Help|help::index> section of this site for a commercial training or consulting company. +Another possibilty is to look in the general L<Getting +Help|help::index> section of this site for a commercial training or +consulting company. =head1 How to Report Problems @@ -34,8 +35,7 @@ =over -=item * Anything in the I<error_log> file that looks suspicious and -possibly related to the problem. +=item * Anything in the I<error_log> file that looks suspicious and possibly related to the problem. =item * Output of C<perl -V> 1.12 +2 -2 modperl-docs/src/docs/1.0/guide/install.pod Index: install.pod =================================================================== RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/install.pod,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- install.pod 26 Apr 2002 18:08:48 -0000 1.11 +++ install.pod 11 May 2002 11:54:44 -0000 1.12 @@ -1886,8 +1886,8 @@ =head2 Compiling libapreq (Apache::Request) with the RH 6.0 mod_perl RPM -Libapreq provides the L<Apache::Request|guide::download/Apache__Request> -module. +Libapreq provides the +L<Apache::Request|download::third_party/Apache__Request> module. Despite many reports of libapreq not working properly with various RPM packages, it is possible to integrate libapreq with mod_perl RPMs. It 1.8 +7 -7 modperl-docs/src/docs/1.0/guide/intro.pod Index: intro.pod =================================================================== RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/intro.pod,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- intro.pod 3 Apr 2002 09:16:08 -0000 1.7 +++ intro.pod 11 May 2002 11:54:44 -0000 1.8 @@ -179,15 +179,15 @@ C<Apache::Registry> and C<Apache::PerlRun> modules. Along with mod_perl related topics, there are many more issues related to administering Apache servers, debugging scripts, using databases, -mod_perl related Perl, code snippets and more. The L<Guide's -Overview|guide::start/> will help you to find your way through the guide. +mod_perl related Perl, code snippets and more. It is assumed that you know at least the basics of building and -installing Perl and Apache. (If you do not, just read the INSTALL documents -which are part of the distribution of each package.) However, in -this guide you will find specific Perl and Apache installation and -configuration notes, which will help you successfully complete the -mod_perl installation and get the server running in a short time. +installing Perl and Apache. (If you do not, just read the INSTALL +documents which are part of the distribution of each package.) +However, in this guide you will find specific Perl and Apache +installation and configuration notes, which will help you successfully +complete the mod_perl installation and get the server running in a +short time. If after reading this guide and the other documents listed in L<Getting Help and Further Learning|guide::help/> you feel that your 1.6 +1 -1 modperl-docs/src/docs/1.0/guide/modules.pod Index: modules.pod =================================================================== RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/modules.pod,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- modules.pod 3 Apr 2002 09:16:08 -0000 1.5 +++ modules.pod 11 May 2002 11:54:44 -0000 1.6 @@ -240,7 +240,7 @@ C<Apache::Request> and libapreq are tied tightly to the Apache API, to which there is no access in a process running under mod_cgi. -(L<Apache::Request|guide::download/Apache__Request>) +(L<Apache::Request|download::third_party/Apache__Request>) =head1 Apache::RequestNotes - Allow Easy, Consistent Access to Cookie and Form Data Across Each Request Phase 1.11 +6 -6 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.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- performance.pod 9 May 2002 10:37:36 -0000 1.10 +++ performance.pod 11 May 2002 11:54:44 -0000 1.11 @@ -77,7 +77,7 @@ =head2 Software Requirements Covered in the section "L<Choosing an Operating -System|guide::hardware/Choosing_an_Operating_System>". +System|general::hardware/Choosing_an_Operating_System>". =head2 Hardware Requirements @@ -134,7 +134,7 @@ but exponentially! More coverage is provided in the section "L<Choosing -Hardware|guide::hardware/Choosing_Hardware>". +Hardware|general::hardware/Choosing_Hardware>". =head1 Essential Tools @@ -337,7 +337,7 @@ Errors: total 299 client-timo 299 socket-timo 0 connrefused 0 connreset 0 Errors: fd-unavail 0 addrunavail 0 ftab-full 0 other 0 -L<httperf download|guide::download/httperf____webserver_Benchmarking_tool> +L<httperf download|download::third_party/httperf____webserver_Benchmarking_tool> =head4 http_load @@ -380,7 +380,7 @@ ./http_load: unknown protocol - -L<http_load download|guide::download/http_load____another_webserver_Benchmarking_tool> +L<http_load download|download::third_party/http_load____another_webserver_Benchmarking_tool> =head4 the crashme Script @@ -4683,7 +4683,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|guide::control/Running_a_Server_in_Single_Proce>". +mode|general::control/Running_a_Server_in_Single_Proce>". =head1 Improving Performance by Prevention @@ -5309,7 +5309,7 @@ If you want to limit number of Apache children that could simultaneously be serving the (nearly) same resource, you should take -a look at the L<C<mod_throttle_access>|guide::download/mod_throttle_access> +a look at the L<C<mod_throttle_access>|download::third_party/mod_throttle_access> module. It solves the problem of too many concurrent request accessing the 1.10 +15 -15 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.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- porting.pod 27 Apr 2002 18:32:39 -0000 1.9 +++ porting.pod 11 May 2002 11:54:44 -0000 1.10 @@ -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|guide::perl/Perl_Reference_> chapter and make sure you +read through the L<Perl Reference|general::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|guide::perl/my_Scoped_Variable_in_Nested_S>. +Nested Subroutines|general::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|guide::perl/Remedies_for_Inner_Subroutines>' discusses +Subroutines|general::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|guide::perl/Tracing_Warnings_Reports>" to learn about +Warnings Reports|general::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|guide::control/Running_a_Server_in_Single_Process_Mode>. +L<single process mode|general::control/Running_a_Server_in_Single_Process_Mode>. To solve this particular C</o> modifier problem refer to L<Compiled -Regular Expressions|guide::perl/Compiled_Regular_Expressions>. +Regular Expressions|general::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|guide::perl/use_require_do_INC_and>. +do(), %INC and @INC Explained|general::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|guide::perl/use_require_do_INC_and>" before you proceed with this +Explained|general::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|guide::control/Restarting_Techniques>. +techniques|general::control/Restarting_Techniques>. After restarting the server about 100 times, you will tire of it and you will look for other solutions. @@ -731,7 +731,7 @@ =head3 Availability -This module is available from L<CPAN|guide::download/CPAN_Downloads>. +This module is available from L<CPAN|download::third_party/CPAN_Downloads>. =head2 Configuration Files: Writing, Dynamically Updating and Reloading @@ -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 |guide::perl/use_require_do_INC_and>. +do(), %INC and @INC |general::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|guide::control/Running_a_Server_in_Single_Proce> to detect this kind of +mode|general::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|guide::perl/Variables_Globally_Lexically_Sc>" for more +and fully qualified|general::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|guide::perl/The_Scope_of_the_Special_Perl_Va> which cannot be +Variables|general::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|guide::correct_headers/> +users|general::correct_headers/> =head1 NPH (Non Parsed Headers) scripts 1.8 +3 -3 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.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- scenario.pod 4 Apr 2002 02:24:28 -0000 1.7 +++ scenario.pod 11 May 2002 11:54:44 -0000 1.8 @@ -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|guide::correct_headers/> to learn more about generating the proper +users|general::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|guide::correct_headers/> to squeeze even more +headers generation tutorial|general::correct_headers/> to squeeze even more power from your servers without investing money in more memory and better hardware. @@ -1474,7 +1474,7 @@ Ask Bjoern Hansen has written the C<mod_proxy_add_forward> module for Apache. It sets the C<X-Forwarded-For> field when doing a C<ProxyPass>, similar to what Squid can do. Its location is specified -in the L<download|guide::download/mod_proxy_add_forward> section. +in the L<download|download::third_party/mod_proxy_add_forward> section. Basically, this module adds an extra HTTP header to proxying requests. You can access that header in the mod_perl-enabled server, and set the 1.8 +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.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- snippets.pod 4 Apr 2002 02:24:28 -0000 1.7 +++ snippets.pod 11 May 2002 11:54:44 -0000 1.8 @@ -26,7 +26,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|guide::perl/Exception_Handling_for_mod_perl>" for more information. +mod_perl|general::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.6 +1 -1 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.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- strategy.pod 13 Apr 2002 19:26:54 -0000 1.5 +++ strategy.pod 11 May 2002 11:54:44 -0000 1.6 @@ -516,7 +516,7 @@ and therefore will not be discussed here. There is a plenty of information available at the Internet though. For more information see L<'High-Availability Linux -Project'|guide::download/High_Availability_Linux_Project>) +Project'|download::third_party/High_Availability_Linux_Project>) =item * 1.10 +7 -7 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.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- troubleshooting.pod 21 Apr 2002 05:00:09 -0000 1.9 +++ troubleshooting.pod 11 May 2002 11:54:44 -0000 1.10 @@ -153,12 +153,12 @@ =head2 Value of $x will not stay shared at - line 5 L<my() Scoped Variable in Nested -Subroutines|guide::perl/my___Scoped_Variable_in_Nested_Subroutines>. +Subroutines|general::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|guide::perl/my___Scoped_Variable_in_Nested_Subroutines>. +Subroutines|general::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|guide::control/Non_Scheduled_Emergency_Log_Rotation>" and "L<All RAM -Consumed|guide::control/All_RAM_Consumed>" +Rotation|general::control/Non_Scheduled_Emergency_Log_Rotation>" and "L<All RAM +Consumed|general::control/All_RAM_Consumed>" =head2 Segfaults when using XML::Parser @@ -278,7 +278,7 @@ There was a bug that reported this debug message regardless of the value of the C<LogLevel> directive. It was fixed in mod_perl 1.19_01 -(L<CVS version|guide::download/mod_perl>). +(L<CVS version|download::third_party/mod_perl>). Generally C<LogLevel> is either C<debug> or C<info>. C<debug> logs everything, C<info> is the next level, which doesn't include debug @@ -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|guide::control/Speeding_up_the_Apache_Termination_and_Restart>" for +Restart|general::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|guide::control/Server_Stopping_and_Restarting> +L<Server Stopping and Restarting|general::control/Server_Stopping_and_Restarting> =head1 Windows OS specific notes 1.2 +6 -6 modperl-docs/src/docs/general/correct_headers.pod Index: correct_headers.pod =================================================================== RCS file: /home/cvs/modperl-docs/src/docs/general/correct_headers.pod,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- correct_headers.pod 11 May 2002 11:36:17 -0000 1.1 +++ correct_headers.pod 11 May 2002 11:54:45 -0000 1.2 @@ -42,16 +42,16 @@ If the number of hits is significant, you might want to consider what cache-friendliness means (you may also want to read -L<[4]|guide::correct_headers/_4_>) and how you can cooperate with caches to +L<[4]|general::correct_headers/_4_>) and how you can cooperate with caches to increase the performance of your site. Especially if you use Squid in accelerator mode (helpful hints for Squid, see -L<[1]|guide::correct_headers/_1_>), you will have a strong motivation to +L<[1]|general::correct_headers/_1_>), you will have a strong motivation to cooperate with it. This document may help you to do it correctly. =head1 Which Headers -The HTTP standard (v 1.1 is specified in L<[3]|guide::correct_headers/_3_>, v -1.0 in L<[2]|guide::correct_headers/_2_>) describes lots of headers. In this +The HTTP standard (v 1.1 is specified in L<[3]|general::correct_headers/_3_>, v +1.0 in L<[2]|general::correct_headers/_2_>) describes lots of headers. In this document, we only discuss those headers which are most relevant to caching. @@ -123,7 +123,7 @@ use Date::Parse; # Date::Parse parses RCS format, Apache::Util::parsedate doesn't $Mtime ||= - Date::Parse::str2time(substr q$Date: 2002/05/11 11:36:17 $, 6); + Date::Parse::str2time(substr q$Date: 2002/05/11 11:54:45 $, 6); $r->set_last_modified($Mtime); =head3 Expires and Cache-Control @@ -531,7 +531,7 @@ value of this method is anything other than C<OK>, you should return that value from your handler and you're done. Apache handles the rest for you. The following example is taken from -L<[5]|guide::correct_headers/_5_>: +L<[5]|general::correct_headers/_5_>: if((my $rc = $r->meets_conditions) != OK) { return $rc; 1.2 +2 -2 modperl-docs/src/docs/general/hardware.pod Index: hardware.pod =================================================================== RCS file: /home/cvs/modperl-docs/src/docs/general/hardware.pod,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- hardware.pod 10 May 2002 07:45:11 -0000 1.1 +++ hardware.pod 11 May 2002 11:54:45 -0000 1.2 @@ -215,7 +215,7 @@ clustering too. There are many load balancing techniques. (See L<High-Availability -Linux Project|guide::download/High_Availability_Linux_Project> for more info.) +Linux Project|download::third_party/High_Availability_Linux_Project> for more info.) =item * @@ -395,7 +395,7 @@ serve one. Now you can calculate how many server processes you need. If you know the maximum size your servers can grow to, you know how much memory you need. If your OS supports L<memory -sharing|guide::hardware/Sharing_Memory>, you can make best use of this +sharing|general::hardware/Sharing_Memory>, you can make best use of this feature by preloading the modules and scripts at server startup, and so you will need less memory than you have calculated. 1.2 +1 -1 modperl-docs/src/docs/general/multiuser.pod Index: multiuser.pod =================================================================== RCS file: /home/cvs/modperl-docs/src/docs/general/multiuser.pod,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- multiuser.pod 10 May 2002 07:45:11 -0000 1.1 +++ multiuser.pod 11 May 2002 11:54:45 -0000 1.2 @@ -166,7 +166,7 @@ Another solution would be to use a setuid startup script, but think twice before you go with it, since if users can modify the scripts they will get a root access. For more information refer to the section -"L<SUID Start-up Scripts|guide::control/SUID_Start_up_Scripts>". +"L<SUID Start-up Scripts|general::control/SUID_Start_up_Scripts>". =item * 1.2 +6 -6 modperl-docs/src/docs/general/perl_reference.pod Index: perl_reference.pod =================================================================== RCS file: /home/cvs/modperl-docs/src/docs/general/perl_reference.pod,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- perl_reference.pod 10 May 2002 07:45:11 -0000 1.1 +++ perl_reference.pod 11 May 2002 11:54:45 -0000 1.2 @@ -365,7 +365,7 @@ =head2 Additional reading references For more information see: L<Using global variables and sharing them -between modules/packages|guide::perl/Using_Global_Variables_and_Shari> and an +between modules/packages|general::perl_reference/Using_Global_Variables_and_Shari> and an article by Mark-Jason Dominus about how Perl handles variables and namespaces, and the difference between C<use vars()> and C<my()> - http://www.plover.com/~mjd/perl/FAQs/Namespaces.html . @@ -754,7 +754,7 @@ First of all there is nothing to worry about, as long as you don't forget to turn the warnings On. If you do happen to have the "L<my() Scoped Variable in Nested -Subroutines|guide::perl/my_Scoped_Variable_in_Nested_S>" +Subroutines|general::perl_reference/my_Scoped_Variable_in_Nested_S>" problem, Perl will always alert you. Given that you have a script that has this problem, what are the ways @@ -1337,7 +1337,7 @@ the suggestion is to put "C<1;>" at the end of file. Although you should use the real filename for most files, if the file -is a L<module|guide::perl/Modules__Libraries_and_Program_Files>, you may use the +is a L<module|general::perl_reference/Modules__Libraries_and_Program_Files>, you may use the following convention instead: require My::Module; @@ -1404,7 +1404,7 @@ use(), just like require(), loads and compiles files containing Perl code, but it works with -L<modules|guide::perl/Modules__Libraries_and_Program_Files> only and +L<modules|general::perl_reference/Modules__Libraries_and_Program_Files> only and is executed at compile time. The only way to pass a module to load is by its module name and not @@ -2480,7 +2480,7 @@ delivering to thousands of users. For similar exception handling techniques, see the section "L<Other -Implementations|guide::perl/Other_Implementations>". +Implementations|general::perl_reference/Other_Implementations>". =head2 The My::Exception class in its entirety @@ -2548,7 +2548,7 @@ =item * Error.pm Graham Barr's excellent OO styled "try, throw, catch" module (from -L<CPAN|guide::download/Perl>). This should be considered your best option +L<CPAN|download::third_party/Perl>). This should be considered your best option for structured exception handling because it is well known and well supported and used by a lot of other applications. 1.1 modperl-docs/src/docs/tutorials/.cvsignore Index: .cvsignore =================================================================== cache.*.dat 1.12 +4 -3 modperl-docs/src/maillist/email-etiquette.pod Index: email-etiquette.pod =================================================================== RCS file: /home/cvs/modperl-docs/src/maillist/email-etiquette.pod,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- email-etiquette.pod 10 May 2002 07:01:22 -0000 1.11 +++ email-etiquette.pod 11 May 2002 11:54:45 -0000 1.12 @@ -30,7 +30,8 @@ Please read the sections on L<getting help with mod_perl 1.x|docs::1.0::guide::help> or L<getting help with mod_perl -2.x|docs::2.0::user::help>, depending on what version you are using. +2.x|docs::2.0::user::help::help>, depending on what version +you are using. =head2 Documentation which comes with the distribution @@ -46,8 +47,8 @@ =head2 Other documentation -There are dozens of references to many authoritative resources in -the L<Offsite Resources|docs::offsite> section. +There are dozens of references to many authoritative resources in the +L<Offsite Resources|docs::offsite::index> section. =head1 How to get on (and off!) the mod_perl mailing list 1.5 +1 -1 modperl-docs/src/products/app-server.pod Index: app-server.pod =================================================================== RCS file: /home/cvs/modperl-docs/src/products/app-server.pod,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- app-server.pod 27 Apr 2002 03:30:10 -0000 1.4 +++ app-server.pod 11 May 2002 11:54:45 -0000 1.5 @@ -9,7 +9,7 @@ coding, or MVC (Model/View/Controller) frameworks. You probably want to look at L<Choosing a Templating -system|docs::2.0::world::templates::choosing> for more information and +system|docs::tutorials::templates::comparison> for more information and in-depth analysis of some of the ones listed here. =head1 Apache::ASP 1.4 +2 -3 modperl-docs/src/start/tips/registry.pod Index: registry.pod =================================================================== RCS file: /home/cvs/modperl-docs/src/start/tips/registry.pod,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- registry.pod 26 Apr 2002 22:41:09 -0000 1.3 +++ registry.pod 11 May 2002 11:54:45 -0000 1.4 @@ -44,9 +44,8 @@ Apache version 1.3.20</small> For more information on running CGI scripts under mod_perl please see -L<CGI to mod_perl FAQ|faqs::cgi_to_mod_perl> and -L<the CGI to mod_perl Porting section|guide::porting> -of L<The Guide|guide::index>. +L<the CGI to mod_perl Porting section|guide::porting> of L<The +Guide|guide::index>. =for html <a class="more" href="../index.html#registry">« back</a>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]