logs
directory. For security reasons, the user account shouldn't have write permissions to the configuration files. If the security of the server is compromised, no one can write to the configuration files.
You can use the account with the name nobody, but this might not work on some systems. Some machines ship with a uid of -2 for the user nobody. A uid less than zero generates an error during installation. Check the /etc/passwd file to see if the uid for nobody exists, and make sure it is greater than zero.
Note
 It's strongly recommended that you use a dedicated account for the server.
The administration server can also run with a user account that must have write permissions to the configuration files for all installed servers. However, it's much easier to run the administration server as root because then it can start and stop servers with port numbers less than 1024. You should shut down the administration server when you're done with it, unless you're using the timing utility to archive log files. For more information about shutting down the administration server, see "Shutting down the administration server" on page 34.
Choose unique port numbers
Port numbers for all network-accessible services are maintained in the file /etc/services. The standard web server port number is 80; the standard SSL-enabled web server port number is 443. You should choose a random number for the administration server to make it harder for anyone to breach your server. When you configure your server, you use the administration server's port number.
Make sure the port you choose isn't in use. Look at the file /etc/services on the server machine to make sure you don't assign a port number that is used by another service. If you choose a port that is being used by another service, the installation will prompt you for another port.
Note
 If you choose a server port number lower than 1024, you must be logged in as root to start the server. After the server is bound to the port, the server changes from root to the user account you specify. If you choose a port number greater than 1024, you don't have to be root to start the server.
Upgrading an existing server
If you're running a 1.1 server, the installation program takes configuration information from your 1.1 server and puts it into a new 2.01 server in a new server root directory (you specify this directory). You should stop running the 1.1 server before upgrading. Make sure you have Netscape Navigator 2.0 or later installed on your computer before upgrading.
To upgrade your existing server,
install
directory that contains the upgrade script and type
./upgrade
httpd.tar
file from the CD-ROM directory to a directory where you want the installation program to run. (The install needs about 30MB of disk space.) This should be a temporary directory and not the directory where you plan to install the server.
*.netscape.com
).
magnus.conf
and obj.conf
. (The server uses these files to control how it works.)
The last step of ns-setup
started your network navigator. If your navigator isn't running, start it. Enter the URL for your server's administration server, using the following format:
http://system_name:admin_port/
where system_name
is the name you entered for your system's full name during installation and admin_port is the administration port you specified (for example, http://server1.acme.com:54321/
).
To configure your web server,
www.acme.com-secure
unsecure_test_area
admin:lnOVeixulqkmU
The text before the colon is the administration user name (in this case, admin); the text following the colon is the password, which is encrypted.
Delete everything after the colon and save the file. Shut down the administration server, and restart it. When prompted for the administration password, don't give one. You should be able to access the administration server now. Be sure to create a new password for the administration server. For more information on changing the administration server password, see "Configuring your administration server" in Chapter 3.