|
|
| |
| |
Upgrading Your Virtual Private Servers
Apache
If you ordered your Virtual Private Servers before March 27, 2000,
and haven't yet upgraded your Apache
Web Server, your Virtual Private Servers HTTP service
is being provided by Apache 1.2.6. See the instructions below that
correspond to your Virtual Private Servers O/S.
-
FreeBSD
Apache 1.3
Connect to your Virtual Private Servers via Telnet
or SSH and do the following.
-
Run the Apache upgrade script
that matches your Virtual Private Servers O/S.
% /usr/local/apache/1.3/bin/updatemyapache
The script will give the following
output:
Apache 1.3 Update
This program updates your apache web server and modules to version 1.3. It will modify your ~/usr/local/etc/httpd/conf/httpd.conf file by removing "#version: 1.2.6" from the very first line. It will also make a new modules directory (~/usr/local/etc/httpd/modules). Your old module directory will be saved to another directory name in ~/usr/local/etc/httpd.
Do you want to continue? [No]: Yes
Checking httpd.conf file...
Updating apache modules...
Updating version number in httpd.conf...
Done: Apache updated from 1.2.6 to 1.3.22
- In Apache 1.2.6, mod_frontpage
and mod_rewrite are statically linked modules. In Apache 1.3,
both of these modules are dynamically linked Modules.
If you are currently using either Microsoft
FrontPage or mod_rewrite, you will need to
explicitly load each module in the web server configuration
file once you have upgraded to Apache 1.3. To do this add
one or both of the following lines to your web server configuration
file (~/www/conf/httpd.conf):
LoadModule frontpage_module modules/mod_frontpage.so
LoadModule rewrite_module modules/mod_rewrite.so
-
Solaris
Apache 1.3
Your Virtual Private Servers is already running the latest version
of Apache. There is no need to upgrade.
-
BSD/OS Upgrade!
The latest version of Apache is unavailable.
-
Huh?
If you don't know the Virtual Private Servers O/S, try the following:
More Information
For more information, see:
|
|