Web
NOTE:
This section only applies if you plan to continue
using the Netscape FastTrack Server
after an Upgrade installation.
You cannot currently use the Internet Manager
to configure the Apache Web Server.
If Netscape FastTrack Server is installed on your system,
the Internet Manager Web button
displays a list of Netscape FastTrack servers that you have configured.
Clicking on a server enables you to configure it using the
Netscape administration utility for that server. This utility
prompts you for a user name and password, which are initially
set to be the same as that for the Internet Manager
(the user name is always admin and the password is
initially set to the first eight characters of the root
password set during the initial system load).
NOTE:
If you change the password for the
Internet Manager, the passwords for
the Netscape administration utilities are not changed.
To change the passwords for the
Netscape administration utilities, you must change them
from within those utilities.
The Netscape administration utilities enable you to change many attributes
of your server's behavior. Some attributes, however, should not be changed,
or the Internet Manager might not work properly. Specifically,
these attributes are:
-
port
-
document root
-
bind to address
-
server name
See also:
Netscape FastTrack Server installation defaults
The installation of the Netscape FastTrack Server
uses the following default values.
You can alter these values once you complete the installation.
Server name-
The string returned by hostname.
Do not change unless you change the system name
(or are configuring multiple servers).
Server IP address-
The first (non-loopback) returned by netstat -in,
or 127.0.0.1 if TCP/IP is not configured.
Do not change unless you change the system's IP address.
NOTE:
Configuring web servers bound to dynamically assigned local
IP addresses (for example, using dynamic PPP)
is not recommended and is unsupported.
Server port-
Netscape FastTrack Server listens on port 80,
is administered on port 620.
Server home-
Netscape FastTrack Server:-
/usr/internet/ns_httpd
Server document root-
Netscape FastTrack Server:-
/usr/internet/ns_httpd/docs
Server processes-
Number of server processes:
Home page-
Netscape FastTrack Server:-
/usr/internet/ns_httpd/docs/index.html
Index files-
index.html or home.html
recorded in the server's root (rather than syslog).
administration username-
Set to admin.
administration password-
Set to the root user's password at installation of server product.
-
The servers run as user nouser.
-
The servers always attempt to resolve IP addresses into host names.
-
All accesses to the servers are logged.
-
Administration access is limited to the local host.
-
The servers use fancy directory indexing.
Starting and restarting Netscape FastTrack servers
Once installed, the Netscape FastTrack Server
starts automatically on reboot.
NOTE:
If you have configured a secure server,
starting the server requires a password,
and therefore must be done manually.
If you have configured
virtual domains,
see
``Configuring interfaces''.
To stop and restart the Netscape server,
use the following commands as root:
Netscape FastTrack Server-
/usr/internet/ns_httpd/httpd-80/stop and
/usr/internet/ns_httpd/httpd-80/start
If a secure server is configured:
/usr/internet/ns_https/https-443/stop and
/usr/internet/ns_https/https-443/start
For more information, see the Netscape FastTrack Server
documentation (but note that the server files are installed
in /usr/internet/ns-httpd on SCO OpenServer).
Deferring or reconfiguring network configuration
During SCO OpenServer installation,
Netscape servers are configured with settings for
Server Name, Hosts, and Addresses by default.
If you defer TCP/IP configuration during initial system
installation or you reconfigure TCP/IP,
any Netscape servers installed on your system might be improperly configured.
To configure your Netscape FastTrack Server after deferring or reconfiguring
networking configuration, edit the following files:
-
In /usr/internet/ns_httpd/admserv/ns-admin.conf,
set ``ServerName'' to the string returned by
hostname(ADMN).
Set ``Hosts'' and ``Addresses'' to the hostnames
and IP addresses allowed to administer this server.
After you set these configuration variables, you can use the
Netscape administration server to further configure the server.
In /usr/internet/ns_httpd/httpd-80/config/magnus.conf,
set ``ServerName'' to the string returned by hostname.
Then copy this file to
/usr/internet/ns_httpd/admserv/httpd-80/magnus.conf.
The timestamp on the former file must be the same or earlier
than that on the latter.
-
If you have enabled virtual domains, edit
/usr/internet/ns_httpd/httpd-80.ipaddress/config/magnus.conf,
where ipaddress is the primary IP address for the system.
Set ``ServerName'' to the string returned by hostname.
Then copy this file to
/usr/internet/ns_httpd/admserv/httpd-80.ipaddress/magnus.conf.
The timestamp on the former file must be the same or earlier
than that on the latter.
If you changed the system's primary IP address, rename these directories:
mv /usr/internet/ns_httpd/httpd-80.OldIPaddress \
/usr/internet/ns_httpd/httpd-80.NewIPaddress
mv /usr/internet/ns_httpd/admserv/httpd-80.OldIPaddress \
/usr/internet/ns_httpd/admserv/httpd-80.NewIPaddress
-
If a secure server is configured, with no virtual domains, in
/usr/internet/ns_https/https-443/config/magnus.conf,
set ``ServerName'' to the string returned by hostname.
Then copy this file to
/usr/internet/ns_httpd/admserv/https-443/magnus.conf.
The timestamp on the former file must be the same or earlier
than that on the latter.
-
If a secure server is configured, with virtual domains enabled, edit
/usr/internet/ns_https/https-443.ipaddress/config/magnus.conf,
where ipaddress is the primary IP address for the system.
Set ``ServerName'' to the string returned by hostname.
Then copy this file to
/usr/internet/ns_httpd/admserv/https-443.ipaddress/magnus.conf.
The timestamp on the former file must be the same or earlier
than that on the latter.
If you changed the system's primary IP address, rename these directories:
mv /usr/internet/ns_https/https-443.OldIPaddress \
/usr/internet/ns_https/https-443.NewIPaddress
mv /usr/internet/ns_httpd/admserv/https-443.OldIPaddress \
/usr/internet/ns_httpd/admserv/https-443.NewIPaddress
Manually configuring Netscape servers
NOTE:
Configuring new servers directly with the
FastTrack Administration Server might cause them not to
be seen by the Internet Manager.
To configure Netscape FastTrack Servers manually
without using the Internet Manager:
-
Start the appropriate administration server by entering this command
as root:
/usr/internet/ns_httpd/start-admin
-
Access the administration server by opening this
URLs, on the server being configured,
with any forms-capable Web browser:
http://localhost:620/
-
Log into the administration server as user admin.
At installation, the admin password was set to
the first eight characters of the root password.
-
Select the server to administer.
-
When you are finished, stop the administration server by entering:
/usr/internet/ns_httpd/stop-admin
Improving Internet server performance
You can improve the performance of your Netscape FastTrack
Internet server by increasing the values of:
These variables are tuned with the Hardware/Kernel Manager
or the configure(ADM) command; see the Performance Guide
for more information.
NSTRPAGES is particularly important if failures are
reported by the netstat -m command.
Increasing NSTRPAGES until the failures no longer
occur is usually appropriate; see ``Tuning STREAMS
usage'' in the ``Tuning networking resources'' chapter
of the Performance Guide. Remember that increasing NSTRPAGES
also affects memory usage.
If you are running a multi-processor system,
it might also be helpful to increase the value of the
str_pool_size variable by editing the
/etc/conf/pack.d/str/space.c file. Make a back-up
copy of this file before making any changes. You must relink
the kernel before modifications to space.c files take
effect. Tuning this variable does not appreciably affect
performance on single-processor systems.
NOTE:
Determining specific values for these parameters depends on your
system hardware, configuration, and usage. We recommend that
you experiment with these values according to the suggestions in
the Performance Guide.
Next topic:
Configuring Domain Name Service (DNS)
Previous topic:
Providing access to unlisted packet filter services
© 2003 Caldera International, Inc. All rights reserved.
SCO OpenServer Release 5.0.7 -- 11 February 2003