Administering the Caching of Web Pages (Tasks)

The following sections cover the system requirements that are needed to use NCA and the procedures to enable or disable parts of the service.

System Requirements for NCA

To support NCA, the system must meet these requirements:

• 256 Mbytes RAM must be installed.

• The Solaris 9 release or one of the Solaris 8 upgrade releases must be installed.

• Apache support must be available. Apache support is available in the Solaris 9 and the Solaris 8 upgrade releases.

This product is intended to be run on a dedicated web server. Running other large processes on a server that runs NCA can cause problems.

How to Enable Caching of Web Pages

1. Become superuser.

2. Register the interfaces.

   Type the names of each of the physical interfaces in the /etc/nca/nca.if file. See the nca.if(4) man page for more information.

   # cat /etc/nca/nca.if hme0 hme1

   Each interface must have an accompanying hostname.interface-name file and an entry in /etc/hosts file for the contents of hostname.interface-name. To start the NCA feature on all interfaces, place an asterisk, *, in the nca.if file.

3. Enable the ncakmod kernel module.

   Change the status entry in /etc/nca/ncakmod.conf to enabled.

   # cat /etc/nca/ncakmod.conf # # NCA Kernel Module Configuration File # status=enabled httpd_door_path=/var/run/nca_httpd_1.door nca_active=disabled

   See the ncakmod.conf(4) man page for more information.

4. Enable NCA logging.

   Change the status entry in /etc/nca/ncalogd.conf to enabled.

   # cat /etc/nca/ncalogd.conf # # NCA Logging Configuration File # status=enabled logd_path_name="/var/nca/log" logd_file_size=1000000

   You can change the location of the log file by changing the path that is indicated by the logd_path_name entry. The log file can be a raw device or a file. See the following examples for samples of NCA log file paths. See the ncalogd.conf(4) man page for more information about the configuration file.

5. For IA only: Increase the virtual memory size.

   Use the eeprom command to set the kernelbase of the system.

   # eeprom kernelbase=0x90000000 # eeprom kernelbase kernelbase=0x90000000

   The second command verifies that the parameter has been set.

   ---

   Note -

   Setting the kernelbase reduces the amount of virtual memory that user processes can use to less than 3 Gbytes. This restriction means that the system is not ABI compliant. When the system boots, the console displays a message that warns you about noncompliance. Most programs do not actually need the full 3-Gbyte virtual address space. If you have a program that needs more than 3 Gbytes, you need to run the program on a system that does not have NCA enabled.

   ---

6. Reboot the server.

Example-Using a Raw Device as the NCA Log File

The logd_path_name string in ncalogd.conf can define a raw device as the place to store the NCA log file. The advantage to using a raw device is that the service can run faster because the overhead in accessing a raw device is less.

The NCA service tests any raw device that is listed in the file to ensure that no file system is in place. This test ensures that no active file systems are accidentally written over.

To prevent this test from finding a file system, run the following command to destroy part of the file system on any disk partition that had been configured as a file system. In this example, /dev/rdsk/c0t0d0s7 is the raw device that has an old file system on it.

# dd if=/dev/zero of=/dev/rdsk/c0t0d0s7 bs=1024 count=1

After running dd, you can then add the raw device to the ncalogd.conf file

# cat /etc/nca/ncalogd.conf
#
# NCA Logging Configuration File
#
status=enabled
logd_path_name="/dev/rdsk/c0t0d0s7"
logd_file_size=1000000

Example-Using Multiple Files for NCA Logging

The logd_path_name string in ncalogd.conf can define multiple targets as the place to store the NCA log file. The second file is used when the first file is full. The following example shows how to select to write to the /var/nca/log file first and then use a raw partition.

# cat /etc/nca/ncalogd.conf
#
# NCA Logging Configuration File
#
status=enabled
logd_path_name="/var/nca/log /dev/rdsk/c0t0d0s7"
logd_file_size=1000000

How to Disable Caching of Web Pages

1. Become superuser.

2. Disable the ncakmod kernel module.

   Change the status entry in /etc/nca/ncakmod.conf to disabled.

   # cat /etc/nca/ncakmod.conf # NCA Kernel Module Configuration File # status=disabled httpd_door_path=/var/run/nca_httpd_1.door nca_active=disabled

   See the ncakmod.conf(4) man page for more information.

3. Disable NCA logging.

   Change the status entry in /etc/nca/ncalogd.conf to disabled.

   # cat /etc/nca/ncalogd.conf # # NCA Logging Configuration File # status=disabled logd_path_name="/var/nca/log" logd_file_size=1000000

   See the ncalogd.conf(4) man page for more information.

4. Reboot the server.

How to Enable or Disable NCA Logging

NCA logging can be turned on or off as needed after NCA has been enabled. See "How to Enable Caching of Web Pages" for more information.

1. Become superuser.

2. Change NCA logging.

   To permanently disable logging, you need to change the status in /etc/nca/ncalogd.conf to disabled and reboot the system. See the ncalogd.conf(4) man page for more information.

   1. Stop logging.

      # /etc/init.d/ncalogd stop

   2. Start logging.

      # /etc/init.d/ncalogd start

How to Load the NCA Socket Utility Library

Follow this process only if your web server does not provide native support of the AF_NCA socket.

Add a line to the web server startup script that causes the library to be preloaded. The line should resemble the following:

LD_PRELOAD=/usr/lib/ncad_addr.so /usr/bin/httpd