We use this script to start and stop PCTs, to start and stop the bebopd, or to ensure the user log file is set up on a node that yod will run on. It is invoked with two options:
user-env start [ bebopd | bebopd+pbs | pct | yod-support] user-env stop [ bebopd | pct ]
The vm-config file determines how the user-env script will be invoked at start-up time.
user-env start bebopd starts the bebopd in the background without any PBS support.
user-env start bebopd+pbs starts the bebopd in PBSupdate mode and allocates some nodes to non-PBS jobs. Edit this if you want to change the number of nodes allocated to non-PBS jobs when the bebopd starts.
user-env start pct mounts the RAM disk required by the PCT and then starts the PCT in the background.
user-env start yod-support ensures that the user log file used by yod is set up on the node. There may be code in the script to create a log file and then make a link to it from /tmp/userlog. (/tmp/userlog is the default location to which yod will write the log file.) The best situation is to have /tmp be on a local disk and to have the yod processes on each service node write the userlog file there. You should edit this section of the file to reflect where you want the userlog file to be. You may not need to invoke it at all, depending on your setup.
The user-env script can be invoked with the stop argument to kill the PCT or to kill the bebopd.