pcs 97/11/25 01:41:46
Modified: . README htdocs/manual install.html Log: Revision Changes Path 1.13 +1 -1 apachen/README Index: README =================================================================== RCS file: /export/home/cvs/apachen/README,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- README 1997/10/19 17:05:04 1.12 +++ README 1997/11/25 09:41:44 1.13 @@ -53,7 +53,7 @@ Finally, make a call to httpd, with a -f to the full path to the httpd.conf file. I.e., the common case: - /usr/local/etc/apache/src/httpd -f /usr/local/etc/apache/conf/httpd.conf + /usr/local/apache/src/httpd -f /usr/local/apache/conf/httpd.conf And voila! The server should be running. 1.16 +2 -2 apachen/htdocs/manual/install.html Index: install.html =================================================================== RCS file: /export/home/cvs/apachen/htdocs/manual/install.html,v retrieving revision 1.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- install.html 1997/10/25 22:35:07 1.15 +++ install.html 1997/11/25 09:41:46 1.16 @@ -169,7 +169,7 @@ location with the -f argument. For example: <PRE> - /usr/local/etc/apache/src/httpd -f /usr/local/etc/apache/conf/httpd.conf + /usr/local/apache/src/httpd -f /usr/local/apache/conf/httpd.conf </PRE> If all goes well this will return to the command prompt almost @@ -228,7 +228,7 @@ the parent. A typical command to stop the server is: <PRE> - kill -TERM `cat /usr/local/etc/apache/logs/httpd.pid` + kill -TERM `cat /usr/local/apache/logs/httpd.pid` </PRE> <P>