Torque behaves strangley when tmpfs is specified as "0" in the disksetup. The setting "0" means "unlimited" - eg, use as much of the memory as is necessary to contain the image. But Torque sees this as a full file system.
When you install Bright Cluster Manager on your system, Bright automatically installs the workload manager of your choice, from among the following:
This article is about how to configure a number of Torque job slots per server, but before I begin, I would like to mention the alternatives you have when you use Bright.
