Peach Configuration

The overall environmental variable for the Peach system must be set for all operations by administrators and users:

setenv PEACH /disk1/Peach

Server configuration

The server is configured using dot files in the main Peach directory.

.Peach: The main configuration file which contains the server location and settings. All job daemons use this file to locate the server and configure communication.
.Peachpath: Specifies all paths to executables for all the platforms.
.Peachpass: The name and password file for user access.
.Peacemail: E-mail addresses for users for notification of job status.

Job daemon configuration

Directories specified in .Peach indicate where the job daemon looks for files and are generated when the server or job daemon is first started. These are the default values:

LOG_DIR => "/var/log/Peach"
CONFIG_DIR => "/etc/Peach"

Each job daemon is configurable through the settings in the file $CONFIG_DIR/.pjobd. This file is set up during job daemon startup if it does not exist, otherwise the existing one is used. The main setting of interest is the number of processors (CPU_NUM_PROCS), which controls the number of jobs the job daemon is allowed to launch. For a multiprocessor computer that may be used intensively outside the context of Peach, a number less than the maximum number of processors may be specified to decrease the load due to Peach.

Each job daemon generates a log of computer activity and job execution in the directory $LOG_DIR.

Restarting the job daemons on reboot

Restarting the job daemons is different on very platform. The files in the next section are automatically generated upon the first use of pjobd on each participating computer. Within the .pjobd file, there is an entry which indicates whether the job daemon will be launched on rebooting the computer. For example this entry indicates that the job daemon will be launched on reboot:

STARTUP_LAUNCH => "1"

Setting the value to "0" will disable the daemons startup on reboot. Whenever there has been a change in the program directories, the startup scripts should be re-generated by typing pjobd_config in the program directory.

Examples of the required startup files automatically generated by pjobd_config or pjobd for the various operating systems

Darwin/MacOSX:
Two files are required:

/Library/StartupItems/PeachJobd/StartupParameters.plist

{
Description     = "Peach Job daemon";
Provides        = ("Job daemon");
Requires        = ("DirectoryServices");
Uses            = ("Disks", "NFS");
OrderPreference = "None";
}

/Library/StartupItems/PeachJobd/PeachJobd

#!/bin/sh

##
# Peach
##

. /etc/rc.common

StartService ()
{
    ConsoleMessage "Starting Peach job daemon"
    export PEACH=/lucy1/Peach
    /lucy1/Peach/pjobd
}

StopService ()
{
    ConsoleMessage "Stopping Peach job daemon"
    /lucy1/Peach/pjobd -stop
}

RestartService ()
{
    ConsoleMessage "Restarting Peach job daemon"
    export PEACH=/lucy1/Peach
    /lucy1/Peach/pjobd
}

RunService "$1"

Linux:

Add a line to the file /etc/rc.local to start the job daemon, e.g.:

/disk1/Peach/pjobd

IRIX64/SGI:
A startup file in the initialization directory is required:
/etc/init.d/PeachJobd

#!/sbin/sh
#
# Peach job daemon startup file
# Bernard Heymann
# 20041026
#

PEACH=/lucy1/Peach
export PEACH

case $1 in
'start')
        $PEACH/pjobd
        ;;
'stop')
        $PEACH/pjobd -stop
        ;;
*)
        echo "usage: PeachJobd {start|stop}"
        ;;
esac

Change the permissions:
chmod 750 PeachJobd

Then create a link from the runlevel 3 directory:

/etc/rc2.d
ln -s ../init.d/PeachJobd S85PeachJobd

OSF1/Alpha:

A startup file in the initialization directory is required:
/sbin/init.d/PeachJobd

Change the permissions:
chmod 750 PeachJobd

Then create a link from the runlevel 3 directory:

/sbin/rc3.d
ln -s ../init.d/PeachJobd S85PeachJobd

Back to Main Page

Updated 2005-02-18, Peter Leong
Updated 2004-11-30, Peter Leong and Bernard Heymann