cvs commit: httpd-docs-1.3/htdocs/manual stopping.html

[sl...@apache.org]

slive       01/02/27 13:42:29

  Modified:    htdocs/manual stopping.html
  Log:
  Move link on httpd command line documentation.  Add link to
  scoreboardfile directive documentation.
  
  Submitted by:	Herve Dumont <hd...@club-internet.fr>
  
  Revision  Changes    Path
  1.18      +4 -3      httpd-docs-1.3/htdocs/manual/stopping.html
  
  Index: stopping.html
  ===================================================================
  RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/stopping.html,v
  retrieving revision 1.17
  retrieving revision 1.18
  diff -u -d -b -u -r1.17 -r1.18
  --- stopping.html	2001/01/28 00:16:07	1.17
  +++ stopping.html	2001/02/27 21:42:28	1.18
  @@ -128,8 +128,8 @@
   This will cause problems if you attempt to restart the server -- it will
   not be able to bind to its listening ports.  Before doing a restart, you
   can check the syntax of the configuration files with the <CODE>-t</CODE>
  -command line argument (see <A HREF="invoking.html">Starting
  -Apache</A>). This still will not guarantee that the server will restart
  +command line argument (see <a href="programs/httpd.html">httpd</a>
  +). This still will not guarantee that the server will restart
   correctly. To check the semantics of the configuration files as well
   as the syntax, you can try starting httpd as a non-root user.  If
   there are no errors it will attempt to open its sockets and logs and
  @@ -158,7 +158,8 @@
   slot.  So it might be advisable to use graceful restarts, with
   an occasional hard restart.  These problems are very difficult to work
   around, but fortunately most architectures do not require a scoreboard file.
  -See the ScoreBoardFile documentation for a method to determine if your
  +See the <a HREF=
  +"mod/core.html#scoreboardfile">ScoreBoardFile</a> documentation for a
   architecture uses it.
   
   <P><CODE>NEXT</CODE> and <CODE>MACHTEN</CODE> (68k only) have small race