If your server will run on one machine among many in a network, you or your system administrator should set up a DNS CNAME record or an alias (such as www) that points to the actual server machine. Later, you can change the actual hostname or IP address of the server machine without having to change all URLs. For example, you might call the server myserver.anycompany.com and then use an alias like www.anycompany.com. So the URLs to documents on your server would always use the www alias instead of myserver.
If you don't know how to create a new user on your system, you should consult your system manual or a good Unix administrator's handbook.You should create a Unix user account for the server. You probably want the server to have restricted access to your system resources and run under a nonprivileged system user account. When the server starts and runs, it runs with this Unix user account (you'll specify this account during installation). Any child processes of the server are created with this account as the owner. The account needs read permissions for the configuration files and write permissions for the
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.
NoteIt's strongly recommended that you use a dedicated account for the server. The administration manager 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 manager as root because then it can start and stop servers with port numbers less than 1024. For security reasons, you must make sure you always shut down the administration manager when you're done with it.
NoteIf 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.
install
directory that contains the upgrade script, and type the following:
#
aix
|
hpux10.X
|
irix
|
sunos4
|
osf_1
|
solaris
|
hpux9.X
|
|
httpd.tar
file from the CD-ROM directory to a directory where you want the installation program to run. (The install needs about 25MB of disk space.) This should be a temporary directory and not the directory where you plan to install the server.
NoteIf you use the Solaris operating system, don't use the /tmp directory because you might encounter problems later in the install process.
*.netscape.com
).
NoteYou do not have to configure your server immediately after installation.
If you don't understand a setting, you can use the default value and later change it via the Server Manager forms.The configuration HTML form collects data that is used to generate the configuration files called
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/
system_name
is the name you entered for your system's full name during installation; admin_port is the administration port you specified (for example, http://server1.acme.com:54321/
).
To configure your new server, do the following:
www.acme.com-unsecure
If your server responds to many requests per day, stopping host name resolution can reduce the load on your DNS or NIS server.
admin:lnOVeixulqkmUThe 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.