The pbs-env script can start the PBS deamons, restart them and stop them. It also sets up a bebopd node so the bebopd can use qmgr to update the PBS server.
pbs-env start [mom|server|scheduler|bebopd-support-only] pbs-env stop [mom|server|scheduler] pbs-env restart [mom|server|scheduler]
There is only one situation where the pbs-env script should not be used to start a PBS daemon. The first time the PBS server is started with a new runtime directory, it should be started with this command:
pbs_server -t create
This informs the server that the database created when you enter the initial qmgr commands to configure the server is not yet set up. If you use the pbs-env script to start the server, no harm is done, but the server will exit with an error.
The pbs-env script assumes there is a template of the PBS runtime directory somewhere. (See the definition of TEMPLATE in the script.) When you run pbs-env start service on a service node, and there is no working directory, the script will create a working directory from this template. So you may wish to edit the script to have the correct path of the working directory template you created when you built and installed the PBS software.
The bebopd-support-only option should more accurately be called pbs-client-support. On any node where PBS clients like qmgr or qsub will be invoked, the PBS runtime directory must be set up. pbs-env start bebopd-support-only ensures there is a PBS runtime directory on the node.