perl-docs-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From s...@apache.org
Subject cvs commit: modperl-docs/src/docs/1.0/guide browserbugs.pod control.pod correct_headers.pod databases.pod dbm.pod frequent.pod help.pod install.pod intro.pod multiuser.pod scenario.pod snippets.pod start.pod troubleshooting.pod
Date Mon, 04 Feb 2002 13:50:25 GMT
stas        02/02/04 05:50:25

  Modified:    src/docs/1.0/guide browserbugs.pod control.pod
                        correct_headers.pod databases.pod dbm.pod
                        frequent.pod help.pod install.pod intro.pod
                        multiuser.pod scenario.pod snippets.pod start.pod
                        troubleshooting.pod
  Log:
  fix broken URLs, sigh :(
  
  Revision  Changes    Path
  1.2       +3 -3      modperl-docs/src/docs/1.0/guide/browserbugs.pod
  
  Index: browserbugs.pod
  ===================================================================
  RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/browserbugs.pod,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- browserbugs.pod	6 Jan 2002 16:54:56 -0000	1.1
  +++ browserbugs.pod	4 Feb 2002 13:50:25 -0000	1.2
  @@ -6,14 +6,14 @@
   
   In a URL which contains a query string, if the string has multiple
   parts separated by ampersands and it contains a key named "reg", for
  -example C<http://my.site.com/foo.pl?foo=bar&reg=foobar>, then some
  +example C<http://example.com/foo.pl?foo=bar&reg=foobar>, then some
   browsers will interpret C<&reg> as an SGML entity and encode it as
   C<&reg;>.  This will result in a corrupted C<QUERY_STRING>. If you
   encounter this problem, then either you should avoid using such keys
   or you should separate parameter pairs with C<;> instead of C<&>.
   C<CGI.pm>, C<Apache::Request> and C<$r-E<gt>args()> support a semicolon
   instead of an ampersand as a separator.  So your URI should look like
  -this: C<http://my.site.com/foo.pl?foo=bar;reg=foobar>.
  +this: C<http://example.com/foo.pl?foo=bar;reg=foobar>.
   
   Note that this is only an issue when you are building your own URLs
   with query strings.  It is not a problem when the URL is the result 
  @@ -27,7 +27,7 @@
   URL.  It drops the port designator and uses port 80 anyway.
   
   See L<Publishing Port Numbers other than
  -80|config/Publishing_Port_Numbers_other_th>.
  +80|config/Publishing_Port_Numbers_other_than_80>.
   
   
   
  
  
  
  1.2       +2 -2      modperl-docs/src/docs/1.0/guide/control.pod
  
  Index: control.pod
  ===================================================================
  RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/control.pod,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- control.pod	6 Jan 2002 16:54:56 -0000	1.1
  +++ control.pod	4 Feb 2002 13:50:25 -0000	1.2
  @@ -53,7 +53,7 @@
   a minus sign, e.g. C<kill -15> or C<kill -TERM> followed by the PID.
   
   
  -=head1 Server Stopping and Restarting 
  +=head1 Server Stopping and Restarting
   
   We will concentrate here on the implications of sending C<TERM>,
   C<HUP>, and C<USR1> signals (as arguments to kill(1)) to a mod_perl
  @@ -1648,7 +1648,7 @@
   be used. The following tips should help you prevent these problems,
   before if at all they hit you.
   
  -=head2 All RAM Consumed 
  +=head2 All RAM Consumed
   
   Sometimes calling an undefined subroutine in a module can cause a
   tight loop that consumes all the available memory.  Here is a way to
  
  
  
  1.2       +2 -4      modperl-docs/src/docs/1.0/guide/correct_headers.pod
  
  Index: correct_headers.pod
  ===================================================================
  RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/correct_headers.pod,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- correct_headers.pod	6 Jan 2002 16:54:56 -0000	1.1
  +++ correct_headers.pod	4 Feb 2002 13:50:25 -0000	1.2
  @@ -118,7 +118,7 @@
     use Date::Parse;
     # Date::Parse parses RCS format, Apache::Util::parsedate doesn't
     $Mtime ||=
  -    Date::Parse::str2time(substr q$Date: 2002/01/06 16:54:56 $, 6);
  +    Date::Parse::str2time(substr q$Date: 2002/02/04 13:50:25 $, 6);
     $r->set_last_modified($Mtime);
   
   =head2 2.1.3) Expires and Cache-Control
  @@ -596,9 +596,7 @@
   
   Lincoln Stein, Doug MacEachern: Writing Apache Modules with Perl and
   C, O'Reilly, 1-56592-567-X. Selected chapters available online at
  -http://www.modperl.com . Amazon page at
  -http://www.amazon.com/exec/obidos/ASIN/156592567X/writinapachemodu/
  -
  +http://www.modperl.com/ .
   
   =head1 Other resources
   
  
  
  
  1.2       +4 -4      modperl-docs/src/docs/1.0/guide/databases.pod
  
  Index: databases.pod
  ===================================================================
  RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/databases.pod,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- databases.pod	6 Jan 2002 16:54:56 -0000	1.1
  +++ databases.pod	4 Feb 2002 13:50:25 -0000	1.2
  @@ -156,8 +156,8 @@
   connection won't be closed either.
   
   See the section L<Handling the 'User pressed Stop button'
  -case|debug/Handling_the_User_pressed_Stop_> for more information on
  -prevention.
  +case|debug/Handling_the__User_pressed_Stop_button__case>
  +for more information on prevention.
   
   =head2 Troubleshooting
   
  @@ -358,8 +358,8 @@
   performance needs.
   
   This is basically a similar idea to having L<two Apache
  -servers|strategy/One_Plain_Apache_and_One_mod_per>, each optimized for
  -its specific requirements.
  +servers|strategy/One_Plain_Apache_and_One_mod_perl_enabled_Apache_Servers>,
  +each optimized for its specific requirements.
   
   
   =head1 Some useful code snippets to be used with relational Databases
  
  
  
  1.2       +1 -1      modperl-docs/src/docs/1.0/guide/dbm.pod
  
  Index: dbm.pod
  ===================================================================
  RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/dbm.pod,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- dbm.pod	6 Jan 2002 16:54:56 -0000	1.1
  +++ dbm.pod	4 Feb 2002 13:50:25 -0000	1.2
  @@ -207,7 +207,7 @@
   
   The result is a starving process, which will timeout the request, and
   it will fail to update the DB.  Ken Williams solved the above problem
  -with his L<C<Tie::DB_Lock>|dbm/mod_perl_and_dbm_files_> module, which is
  +with his L<C<Tie::DB_Lock>|dbm/mod_perl_and_dbm> module, which is
   discussed in one of the following sections.
   
   There are several locking wrappers for C<DB_File> in CPAN right now.
  
  
  
  1.2       +2 -2      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.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- frequent.pod	6 Jan 2002 16:54:56 -0000	1.1
  +++ frequent.pod	4 Feb 2002 13:50:25 -0000	1.2
  @@ -13,14 +13,14 @@
   =head1 my() scoped variable in nested subroutines
   
   See the section "L<my() Scoped Variable in Nested 
  -Subroutines|perl/my_Scoped_Variable_in_Nested_S>".
  +Subroutines|perl/my___Scoped_Variable_in_Nested_Subroutines>".
   
   
   
   =head1 Segfaults caused by PerlFreshRestart
   
   See the section L<Evil things might happen when using
  -PerlFreshRestart|troubleshooting/Evil_things_might_happen_when_us>
  +PerlFreshRestart|troubleshooting/Evil_things_might_happen_when_using_PerlFreshRestart>
   
   
   =cut
  
  
  
  1.2       +9 -16     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.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- help.pod	6 Jan 2002 16:54:56 -0000	1.1
  +++ help.pod	4 Feb 2002 13:50:25 -0000	1.2
  @@ -285,10 +285,6 @@
   
   =over
   
  -=item * PerlMonth
  -
  -http://perlmonth.com
  -
   =item * ApacheToday
   
   http://apachetoday.com
  @@ -476,12 +472,12 @@
   http://search.cpan.org/search?dist=CookBookA
   http://search.cpan.org/search?dist=CookBookB
   
  -a series of articles at PerlMonth.com by Steven McDougall:
  -http://www.perlmonth.com/columns/modules/modules.html?issue=6
  -http://www.perlmonth.com/columns/modules/modules.html?issue=7
  -http://www.perlmonth.com/columns/modules/modules.html?issue=8
  -http://www.perlmonth.com/columns/modules/modules.html?issue=9
  -http://www.perlmonth.com/columns/modules/modules.html?issue=10
  +a series of articles by Steven McDougall:
  +http://world.std.com/~swmcd/steven/perl/pm/xs/intro/index.html
  +http://world.std.com/~swmcd/steven/perl/pm/xs/concepts.html
  +http://world.std.com/~swmcd/steven/perl/pm/xs/tools/index.html
  +http://world.std.com/~swmcd/steven/perl/pm/xs/modules/modules.html
  +http://world.std.com/~swmcd/steven/perl/pm/xs/nw/NW.html
   
   I<Advanced Perl Programming> By Sriram Srinivasan. Published by
   O'Reilly & Associates. ISBN: 1-56592-220-4. Chapters 18-20.
  @@ -526,9 +522,6 @@
   
   =back
   
  -See also http://tile.net/listserv/perl5portersdigest.html and
  -http://tile.net/lists/perl5porters.html .
  -
   List's archive is available at
   http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/.
   
  @@ -631,7 +624,7 @@
   http://linuxplanet.com/linuxplanet/print/1445/
   
   Installing and Securing the Apache Webserver with SSL
  -http://www.securityfocus.com/focus/sun/articles/apache-inst.html?&_ref=1653102939
  +http://www.securityfocus.com/infocus/1356
   
   
   =item * mod_throttle_access
  @@ -657,7 +650,7 @@
   =item *
   
   Introduction to Structured Query Language:
  -http://w3.one.net/~jhoffman/sqltut.htm
  +http://www.dbbm.fiocruz.br/class/Lecture/d17/sql/jhoffman/sqltut.html
   
   =item *
   
  @@ -679,7 +672,7 @@
   
   =item * DBI mailing list archives
   
  -http://outside.organic.com/mail-archives/dbi-users/
  +http://www.bitmechanic.com/mail-archives/dbi-users/
   http://www.xray.mpe.mpg.de/mailing-lists/dbi/
   
   =back
  
  
  
  1.2       +13 -13    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.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- install.pod	6 Jan 2002 16:54:56 -0000	1.1
  +++ install.pod	4 Feb 2002 13:50:25 -0000	1.2
  @@ -582,8 +582,8 @@
   installed.
   
   The most frequent pitfall is a missing gdbm library.  See L<Missing or
  -Misconfigured libgdbm.so|install/Missing_or_Misconfigured_libgdbm> for
  -more info.
  +Misconfigured libgdbm.so|install/Missing_or_Misconfigured_libgdbm_so>
  +for more info.
   
   But why guess, when we can actually see the real error message and
   understand what the real problem is.  To get a real error message,
  @@ -1919,7 +1919,7 @@
   
   David Harris has started an effort to build better RPM/SRPM mod_perl
   packages.  You will find the link to David's site from
  -http://perl.apache.org/distributions.html.
  +http://perl.apache.org/download/distributions.html .
   
   Features of this RPM:
   
  @@ -2117,10 +2117,11 @@
   a surprise.  Installing the Apache RPM will go just fine, and
   http://localhost will bring up some type of web page for you.
   However, after installation of the mod_perl RPM, the L<How can I tell
  -whether mod_perl is running|install/How_can_I_tell_whether_mod_perl_>
  -test will show that Apache is not mod_perl enabled.  This is because
  -mod_perl needs to be added as a separate module using Apache's Dynamic
  -Shared Objects.
  +whether mod_perl is
  +running|install/How_can_I_tell_whether_mod_perl_is_running_> test will
  +show that Apache is not mod_perl enabled.  This is because mod_perl
  +needs to be added as a separate module using Apache's Dynamic Shared
  +Objects.
   
   To use mod_perl as a DSO, make the following modifications to your
   Apache configuration files:
  @@ -2738,7 +2739,7 @@
   =item *
   
   Reduce resources usage (see L<Limiting the size of the
  -processes|performance/Limiting_the_Size_of_the_Process>).
  +processes|performance/Limiting_the_Size_of_the_Processes>).
   
   =item *
   
  @@ -3029,8 +3030,8 @@
   takes care of overriding the C<exit()> call for you, so it's not an
   issue.  For reasons and implementations see: L<Terminating requests
   and processes, exit()
  -function|porting/Terminating_requests_and_process> and also L<Writing
  -Mod Perl scripts and Porting plain CGIs to
  +function|porting/Terminating_requests_and_processes__the_exit___and_child_terminate___functions>
  +and also L<Writing Mod Perl scripts and Porting plain CGIs to
   it|porting/>.
   
   =head2 Testing via lwp-request
  @@ -3050,9 +3051,8 @@
   
   To see the server version only.
   
  -Use C<http://www.example.com:port_number> if your server is listening
  -to a port other than port 80.
  -
  +Specify the port number if your server is listening to a port other
  +than port 80. For example: C<http://www.example.com:8080>.
   
   =head1 General Notes
   
  
  
  
  1.2       +1 -1      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.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- intro.pod	6 Jan 2002 16:54:56 -0000	1.1
  +++ intro.pod	4 Feb 2002 13:50:25 -0000	1.2
  @@ -274,7 +274,7 @@
   1,603,000 unique visitors/month Aug-1999
   
   http://www.flash.net
  -http://www.mediametrix.com/TopRankings/TopRankings.html
  +http://www.mediametrix.com/
   
   Apache/1.2.4 mod_perl/1.00 on Solaris
   
  
  
  
  1.3       +6 -6      modperl-docs/src/docs/1.0/guide/multiuser.pod
  
  Index: multiuser.pod
  ===================================================================
  RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/multiuser.pod,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- multiuser.pod	4 Feb 2002 12:12:10 -0000	1.2
  +++ multiuser.pod	4 Feb 2002 13:50:25 -0000	1.3
  @@ -47,7 +47,7 @@
   write) any other files that belong to the same user and/or group the
   web server is running as.  Note that L<it's impossible to run
   C<suEXEC> and C<cgiwrap> extensions under
  -mod_perl|install/Is_it_possible_to_run_mod_perl_e>.
  +mod_perl|install/Is_it_possible_to_run_mod_perl_enabled_Apache_as_suExec_>.
   
   Another issue is the security of the database connections.  If you use
   C<Apache::DBI>, by hacking the C<Apache::DBI> code you can pick a
  @@ -262,9 +262,9 @@
   Allows running a few instances of the same or different OSs on the
   same machine. This technology comes in two flavors:
   
  -open source: http://www.freemware.org/ also known as plex86
  +Open source: http://www.plex86.org/
   
  -commercial: http://www.vmware.com/
  +Commercial: http://www.vmware.com/
   
   So you may want to run a separate OS for each of your clients
   
  @@ -310,12 +310,12 @@
   mod_macro|config/Configuring_Apache___mod_perl_with_mod_macro>
   
   L<Is There a Way to Provide a Different startup.pl File for Each
  -Individual Virtual Host|config/Is_There_a_Way_to_Provide_a_Diff>
  +Individual Virtual Host|config/Is_There_a_Way_to_Provide_a_Different_startup_pl_File_for_Each_Individual_Virtual_Host>
   
   L<Is There a Way to Modify @INC on a Per-Virtual-Host or Per-Location
  -Basis.|config/Is_There_a_Way_to_Modify_INC_on> 
  +Basis.|config/Is_There_a_Way_to_Modify__INC_on_a_Per_Virtual_Host_or_Per_Location_Basis_>

   
   L<A Script From One Virtual Host Calls a Script with the Same Path
  -From the Other Virtual Host|config/A_Script_From_One_Virtual_Host_C>
  +From the Other Virtual Host|config/A_Script_From_One_Virtual_Host_Calls_a_Script_with_the_Same_Path_From_the_Other_Virtual_Host>
   
   =cut
  
  
  
  1.2       +12 -11    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.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- scenario.pod	6 Jan 2002 16:54:56 -0000	1.1
  +++ scenario.pod	4 Feb 2002 13:50:25 -0000	1.2
  @@ -85,8 +85,8 @@
       DO_HTTPD=1 USE_APACI=1 EVERYTHING=1
   
   There are many additional optional parameters.  You can find some of
  -them later in this section and in the L<Server Configuration|config/mod_perl_Configuration_>
  -section.
  +them later in this section and in the L<Server
  +Configuration|config/mod_perl_Configuration> section.
   
   While running C<perl Makefile.PL ...> the process will check for
   prerequisites and tell you if something is missing.  If you are
  @@ -238,7 +238,8 @@
   not work and they may exhibit strange behaviour.  Depending on the
   degree of sloppiness they may need anything from minor tweaking to a
   major rewrite to make them work properly.  (See L<Sometimes My Script
  -Works, Sometimes It Does Not|debug/Sometimes_My_Script_Works_Somet> )
  +Works, Sometimes It Does 
  +Not|debug/Sometimes_My_Script_Works__Sometimes_It_Does_Not> )
   
   The above setup is very basic, but as with Perl, you can start to
   benefit from mod_perl from the very first moment you try it.  As you
  @@ -428,8 +429,8 @@
   [META:
   It's very important to use the same compiler you build the perl with.
   See the section 'L<What Compiler Should Be Used to Build
  -mod_perl|install/What_Compiler_Should_Be_Used_to_>' for more
  -information.
  +mod_perl|install/What_Compiler_Should_Be_Used_to_Build_mod_perl_>' 
  +for more information.
   
   [META: --- Hmm, what's the option that overrides the compiler when
   building Apache from mod_perl. Check also whether mod_perl supplies
  @@ -462,7 +463,7 @@
   While doing C<perl Makefile.PL ...> mod_perl might complain by warning
   you about a missing library C<libgdbm>. This is a crucial warning. See
   L<Missing or Misconfigured
  -libgdbm.so|install/Missing_or_Misconfigured_libgdbm> for more info.
  +libgdbm.so|install/Missing_or_Misconfigured_libgdbm_so> for more info.
   
   Now rename C<httpd> to C<httpd_perl>:
   
  @@ -524,12 +525,12 @@
   server like Squid.
   
   For more details see L<Publishing Port Numbers other than
  -80|config/Publishing_Port_Numbers_other_th>, L<Running One Webserver
  +80|config/Publishing_Port_Numbers_other_than_80>, L<Running One Webserver
   and Squid in httpd Accelerator
  -Mode|scenario/Running_One_Webserver_and_Squid_>, L<Running Two
  -Webservers and Squid in httpd Accelerator
  -Mode|scenario/Running_Two_webservers_and_Squid> and L<Using
  -mod_proxy|scenario/mod_proxy>.
  +Mode|scenario/Running_One_Webserver_and_Squid_in_httpd_Accelerator_Mode>,
  +L<Running Two Webservers and Squid in httpd Accelerator
  +Mode|scenario/Running_Two_webservers_and_Squid_in_httpd_Accelerator_Mode>
  +and L<Using mod_proxy|scenario/mod_proxy>.
   
   Now we proceed to the mod_perl specific directives.  It will be a good
   idea to add them all at the end of C<httpd.conf>, since you are going
  
  
  
  1.2       +5 -8      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.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- snippets.pod	6 Jan 2002 16:54:56 -0000	1.1
  +++ snippets.pod	4 Feb 2002 13:50:25 -0000	1.2
  @@ -3,9 +3,6 @@
   Code Snippets
   
   
  -
  -
  -
   =head1 Redirecting Errors to the Client Instead of error_log
   
   Many error conditions result in an I<exception> (or I<signal> -- same
  @@ -924,9 +921,9 @@
   
   So if a client submits a request of this kind:
   
  -  http://www.example.com/news/?uri=http://www.example-2.com/
  +  http://www.example.com/news/?uri=http://www2.example.com/
   
  -C<$uri> will hold I<http://www.example-2.com/news/> and that's where
  +C<$uri> will hold I<http://www2.example.com/news/> and that's where
   the request will be redirected.
   
   
  @@ -1274,10 +1271,10 @@
   log_status() method? or at least an C<Apache::LOG_HANDLER_RESULT>
   config variable?).
   
  -In the meantime, there's
  -L<Apache::RedirectLogFix|snippets/Code_Snippets_>.
  +In the meantime, there's C<Apache::RedirectLogFix>, distributed with
  +mod_perl.
   
  -Put this in your I<httpd.conf>
  +Add to your I<httpd.conf>:
   
     PerlLogHandler Apache::RedirectLogFix
   
  
  
  
  1.2       +8 -8      modperl-docs/src/docs/1.0/guide/start.pod
  
  Index: start.pod
  ===================================================================
  RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/start.pod,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- start.pod	6 Jan 2002 16:54:56 -0000	1.1
  +++ start.pod	4 Feb 2002 13:50:25 -0000	1.2
  @@ -83,12 +83,12 @@
   in a matter of minutes, and more.
   
   (META: fix this)
  -The L<mod_perl Status. Peeking into the Server's Perl Innards|config/mod_perl_Configuration_>
  -chapter shows you the ways you can peek at what is going on in a
  -mod_perl-enabled server while it is running. Like looking at the value
  -of some global variable, what database connections are open, looking
  -up what modules are loaded and their paths, what is the value of
  -C<@INC>, and much more.
  +The L<mod_perl Status. Peeking into the Server's Perl
  +Innards|config/mod_perl_Configuration> chapter shows you the ways you
  +can peek at what is going on in a mod_perl-enabled server while it is
  +running. Like looking at the value of some global variable, what
  +database connections are open, looking up what modules are loaded and
  +their paths, what is the value of C<@INC>, and much more.
   
   Every programmer needs to know how to debug her program. It is an
   _easy_ task with plain Perl. Just invoke the program with the C<-d>
  @@ -124,8 +124,8 @@
   gives you an idea on how to choose the software and hardware for the
   webserver.
   
  -The L<mod_perl Advocacy|advocacy/mod_perl_Advocacy_> tries to make it
  -easier to advocate mod_perl around the world.
  +The L<mod_perl Advocacy|advocacy/> tries to make it easier to advocate
  +mod_perl around the world.
   
   The L<Getting Help and Further Learning|help/> chapter refers you to
   other related information resources, like learning Perl programming
  
  
  
  1.2       +14 -13    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.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- troubleshooting.pod	6 Jan 2002 16:54:56 -0000	1.1
  +++ troubleshooting.pod	4 Feb 2002 13:50:25 -0000	1.2
  @@ -193,7 +193,7 @@
   =head2 Value of $x will not stay shared at - line 5
   
   L<my() Scoped Variable in Nested 
  -Subroutines|perl/my_Scoped_Variable_in_Nested_S>.
  +Subroutines|perl/my___Scoped_Variable_in_Nested_Subroutines>.
   
   
   
  @@ -205,7 +205,7 @@
   =head2 Value of $x may be unavailable at - line 5.
   
   L<my() Scoped Variable in Nested 
  -Subroutines|perl/my_Scoped_Variable_in_Nested_S>.
  +Subroutines|perl/my___Scoped_Variable_in_Nested_Subroutines>.
   
   
   
  @@ -251,7 +251,7 @@
   Most often you will find that you really do have a syntax error.
   However the other reason might be that a script running under
   C<Apache::Registry> is using C<__DATA__> or C<__END__> tokens. L<Learn
  -why|porting/_END_and_DATA_tokens>.
  +why|porting/__END___and___DATA___tokens>.
   
   
   
  @@ -332,7 +332,7 @@
   =head2 Preventing mod_perl Processes From Going Wild
   
   See the sections "L<Non-Scheduled Emergency Log
  -Rotation|control/Non_Scheduled_Emergency_Log_Rota>" and "L<All RAM
  +Rotation|control/Non_Scheduled_Emergency_Log_Rotation>" and "L<All RAM
   Consumed|control/All_RAM_Consumed>"
   
   
  @@ -351,14 +351,14 @@
   =head2 My CGI/Perl Code Gets Returned as Plain Text Instead of Being Executed by the Webserver
   
   See L<My CGI/Perl Code Gets Returned as Plain Text Instead of Being
  -Executed by the Webserver|config/My_CGI_Perl_Code_Gets_Returned_a>.
  +Executed by the Webserver|config/My_CGI_Perl_Code_Gets_Returned_as_Plain_Text_Instead_of_Being_Executed_by_the_Webserver>.
   
   
   
   =head2 Incorrect line number reporting in error/warn log messages
   
   See L<Use of uninitialized value at (eval 80) line
  -12.|troubleshooting/Use_of_uninitialized_value_at_e>
  +12.|troubleshooting/Use_of_uninitialized_value_at__eval_80__line_12_>
   
   
   
  @@ -397,8 +397,9 @@
   which is called if a connection times out or if the client presses the
   'Stop' button.  It gives you an opportunity to do cleanups if the
   script was aborted in the middle of its execution.  See L<Handling the
  -'User pressed Stop button' case|debug/Handling_the_User_pressed_Stop_>
  -for more info.
  +'User pressed Stop button'
  +case|debug/Handling_the__User_pressed_Stop_button__case> for more
  +info.
   
   If your mod_perl version is earlier than 1.17 you might also get the 
   message in the following section...
  @@ -496,12 +497,12 @@
   empty string in our example).
   
   Also read about L<Finding the Line Which Triggered the Error or
  -Warning|debug/Finding_the_Line_Which_Triggered>.
  +Warning|debug/Finding_the_Line_Which_Triggered_the_Error_or_Warning>.
   
   =head2 Undefined subroutine &Apache::ROOT::perl::test_2epl::some_function called at
   
   See L<Names collisions with Modules and
  -libs|porting/Name_collisions_with_Modules_and>.
  +libs|porting/Name_collisions_with_Modules_and_libs>.
   
   
   
  @@ -530,7 +531,7 @@
   Perl 5.005+ plus is recommended for its improved malloc.c and other
   features that improve mod_perl and are turned on by default.
   
  -See also L</Out_of_memory!>
  +See also L</Out_of_memory_>
   
   =head2 Out of memory!
   
  @@ -705,8 +706,8 @@
   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|control/Speeding_up_the_Apache_Terminati>" for more 
  -information.
  +Restart|control/Speeding_up_the_Apache_Termination_and_Restart>" for 
  +more information.
   
   
   =head2 httpd keeps on growing after each restart
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-cvs-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-cvs-help@perl.apache.org


Mime
View raw message