Commit a2344496 authored by Joshua Slive's avatar Joshua Slive
Browse files

Move link on httpd command line documentation. Add link to 

scoreboardfile directive documentation.

Submitted by:	Herve Dumont <hdumont@club-internet.fr>


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@88374 13f79535-47bb-0310-9956-ffa450edef68
parent fb885ba7

docs/manual/stopping.html

+11 −10
Original line number Diff line number Diff line
@@ -115,15 +115,15 @@ are "gracefully exiting" by handling their last request.) 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 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 fail because it's not root (or because the currently running httpd

already has those ports bound).  If it fails for any other reason then

it's probably a config file error and the error should be fixed before

issuing the graceful 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 fail because it's not root (or because the

currently running httpd already has those ports bound).  If it fails

for any other reason then it's probably a config file error and the

error should be fixed before issuing the graceful restart.





<H3>Restart Now</H3>
@@ -167,7 +167,8 @@ a fatal error, while the latter just causes the server to lose a scoreboard 
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

docs/manual/stopping.html.en

+11 −10
Original line number Diff line number Diff line
@@ -115,15 +115,15 @@ are "gracefully exiting" by handling their last request.) 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 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 fail because it's not root (or because the currently running httpd

already has those ports bound).  If it fails for any other reason then

it's probably a config file error and the error should be fixed before

issuing the graceful 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 fail because it's not root (or because the

currently running httpd already has those ports bound).  If it fails

for any other reason then it's probably a config file error and the

error should be fixed before issuing the graceful restart.





<H3>Restart Now</H3>
@@ -167,7 +167,8 @@ a fatal error, while the latter just causes the server to lose a scoreboard 
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