Configuration files

The entries in the configuration files list nodes that PBS daemons will accept messages from, determine how the MOM copies the .e and .o files to the user's submission directory, and so on. Certain problems that occur at runtime may be due to incorrect or missing entries. Sample files and a detailed README file are in the source code repository [3]. The files you would most commonly need to check are these:

• /tmp/pbs/working/mom_priv/config
  • The $clienthost directives in this file should list every node on which a PBS server, scheduler or MOM is running. These are the nodes that the MOM will accept messages from.
  • The $usecp directives should contain the pathname prefix for all user directories that are mounted on the service nodes. If a directory is not listed here, the MOM will try to use PBS's own version of rcp (rather than cp) to copy the user's .e and .o files back to their submission directory. The pbs_rcp command may fail if certain permissions are not set correctly, and also may take longer than cp.

• /tmp/pbs/working/sched_priv/usage

  This is the file in which the scheduler keeps track of the individual users' usage of the machine. It uses these figures in deciding whose job to schedule next. On a new system, the usage file must be created (0 length, permission 644) or the scheduler will report an error.

• /tmp/pbs/working/server_priv/nodes

  This file should list every node on which a PBS MOM will run, followed by the modifier :ts indicating that it is timeshared, i.e. more than one PBS job may run on the node at any given time. Warning: a blank line at the end of this file will cause the PBS server to exit with an error.

• /tmp/pbs/working/PBSserver

  This file names the node on which the PBS server is running.