From 0787adf1173245c68e4631d510d807bdcc6937de Mon Sep 17 00:00:00 2001
From: Jeff Trawick
LocalSystem is a very privileged account locally, so you @@ -173,9 +173,9 @@ DCOM, or secure RPC.-
NEVER grant network privilages to the SYSTEM
+ NEVER grant network privileges to the SYSTEM
account! Create a new user account instead, grant the
- appropriate privilages to that user, and use the the 'Log On
+ appropriate privileges to that user, and use the the 'Log On
As:' option. Select the Start Menu -> Settings -> Control
Panel -> Services -> apache service ... and click the
"Startup" button to access this setting. The SYSTEM account has no privilages to the network, so
+ The SYSTEM account has no privileges to the network, so
shared pages or a shared installation of Apache is invisible to
the service. If you intend to use any network
resources, the following steps should help: If you allow the account to log in as a user, then you can
- log in yourself and test that the account has the privilages to
+ log in yourself and test that the account has the privileges to
execute the scripts, read the web pages, and that you can start
Apache in a console window. If this works, and you have
followed the steps above, Apache should execute as a service
@@ -356,7 +356,7 @@
menu or desktop to perform the required action. Apache and Windows 95/98 offer no support for running the
- Apache service as a specific user with network privilages. In
+ Apache service as a specific user with network privileges. In
fact, Windows 95/98 offers no security on the local machine,
either. This is the simple reason that the Apache Software
Foundation never endorses the use of Windows 95/98 as a public
--
2.40.0