Previous PageNext Page

3.2.8 System File Relocation

For users installing Chili!Soft ASP to shared file systems such as NFS or AFS (Andrew File System), or who are setting up a shared, multi-machine installation of Chili!Soft ASP, please refer to the following instructions. If you are not doing any of the above, it is recommended that you not alter the locations of the Chili!Soft ASP system files.
 

3.2.8.1 Relocating the Registry File

One of the key system files of Chili!Soft ASP called the Registry File (registry.bin) must be located on a local file system that supports file locking for proper operation. During Chili!Soft ASP installation, the installer will create a script named mwsetup.sh in the installation directory (the default is /opt/casp). Contained within this file is a line resembling
 

MWREGISTRY=<path name>/registry.bin

where <path name> is the current location of the registry file. The following steps will describe how to relocate the registry file.
 
  • Write down the current value of <path name>.
  • Create the new directory where you wish to relocate the registry file. This directory MUST reside on the local machine where the file system supports file locking. For the following steps, this new directory will be referred to as <new path name>.
  • Edit mwsetup.sh with a text editor such as vi and change the line
  • MWREGISTRY=<path name>/registry.bin

    to
     

    MWREGISTRY=<new path name>/registry.bin

  • Copy the registry file from its old location (<path name>/registry.bin) to its new location (i.e. <new path name>/registry.bin).

Note:

If you are creating a multi-machine installation of Chili!Soft ASP, you will need a separate copy of registry.bin on each machine running Chili!Soft ASP. Also, each local file system must have the identical local path to the location of the registry.bin file (i.e. /path/to/registry/file must exist on each machine.)

3.2.8.2 Relocating Chili!Soft ASP PID Files

For users wishing to install Chili!Soft ASP to a shared file system, but move Chili!Soft ASP writable files to a local file system, Chili!Soft ASP provides a mechanism to allow for this. For single machine Chili!Soft ASP installations, this is not required, but has the added benefit that it may decrease network congestion. For multi-machine Chili!Soft ASP installations, the PID files may not be shared by Chili!Soft ASP engines and must be relocated (see the Multi-Machine Chili!Soft ASP
 
section for more information.)
 
There are three attributes of importance in the casp.cnfg file (which is contained under each asp-<server>-<port> directory). These are the hashobj_pid and logfile attributes (located in the [machines] section), and the caspd_pid attribute (located in the [default machine] section). These attributes allow you to specify the locations of the two PID files. If you need to relocate these files, remember these two important facts:
 
  • If you have several Chili!Soft ASP installations on a single physical server (with separate asp-<server>-<port> directories), then the casp.cnfg file in each directory may point to common directories for the PID and log files, but must point to different file names for the PID and log files.
  • If you have a multi-machine installation of Chili!Soft ASP, then each machine that is hosting the Chili!Soft ASP engine must have its own copy of the PID files. Because the casp.cnfg file must be identical for each machine in a multi-machine installation, the directories and filenames for the PID and log files specified in casp.cnfg must exist on each machine's local file system.
Example:
 
Suppose the [machines] and [default machine] sections of your current casp.cnfg file resemble the following.
 

[machines]

count=1

machine1=127.0.0.1

portnumber=4330

logfile=/opt/casp/logs/server-4330

mtengine=0

disablerestart=0

hashobj_pid=/opt/casp/logs/asp-apache-4330/hashobj.pid

[default machine]

caspd_pid=/opt/casp/logs/asp-apache-4330/caspd.pid

maxprocesses=1

inherit_user=1

#user=nobody

#group=nobody

And you wished to relocate all of your files off of the shared /opt directory to a /usr/local/casp directory. To do this, you would follow these steps.
 
  • Create the destination directory(ies). Example:
  • mkdir -p /usr/local/casp/pids

    mkdir -p /usr/local/casp/logs

  • Edit the casp.cnfg file to resemble the following example:
  • [machines]

    count=1

    machine1=127.0.0.1

    portnumber=4330

    logfile=/usr/local/casp/logs/server-4330

    mtengine=0

    disablerestart=0

    hashobj_pid=/usr/local/casp/pids/hashobj-4330.pid

    [default machine]

    caspd_pid=/usr/local/casp/pids/caspd-4330.pid

    maxprocesses=1

    inherit_user=1

    #user=nobody

    #group=nobody

  • Last, copy the server log file and the PID files to the director(ies) you've created.

Note:

If you are creating a multi-machine installation of Chili!Soft ASP, remember to copy the log file and PID files to each machine running Chili!Soft ASP. Also, each local file system must have the identical local path to the location of the log and PID files (i.e. according to the above example, /usr/local/casp/logs and /usr/local/casp/pids must exist on each machine.)


Copyright © 2000 Chili!Soft

Previous PageTop Of PageNext Page