PAR Technologies V5 Washer User Manual


 
38 ParaStation5 Administrator's Guide
accounter
This is actually a pseudo communication layer. It is only used for configuring nodes running the
ParaStation accounting daemon and should be used only in a particular Nodes entry.
NrOfNodes num
Define the number of connected nodes including the frontend node. The nodes will be numbered 0
num-1.
There is no default value for NrOfNodes. NrOfNodes has to be declared within
the configuration file in any case.
The number of connected nodes has to be declared before any Nodes.
HWType { ethernet | p4sock | openib | mvapi | gm | elan | dapl | none }
HWType { { ethernet | p4sock | openib | mvapi | gm | elan | dapl | none }... }
Define the default communication hardware available on the nodes of the ParaStation cluster. This
may be overruled by an explicit HWType option in a Node statement.
The hardware types used within this command have to be defined in Hardware declarations before.
Further hardware declarations might be defined by the user, but this is pretty much undocumented.
It is possible to enable more than one hardware type, either as default or on a per node basis.
The default value of HWType is none.
starter { true | yes | 1 | false | no | 0 }
If the argument is one of yes, true or 1, all nodes declared within a Node statement will allow to start
parallel tasks, unless otherwise stated.
If the argument is one of no, false or 0, starting will be not allowed.
It might be useful to prohibit the startup of parallel task from the frontend machine if a batch system is
used. This will force all users to use the batch system in order to start their tasks. Otherwise it would
be possible to circumvent the batch system by starting parallel task directly from the frontend machine.
The default is to allow the starting of parallel tasks from all nodes.
runJobs { true | yes | 1 | false | no | 0 }
If the argument is one of yes, true or 1, all nodes declared within a Node statement will allow to run
processes of parallel tasks, unless otherwise stated.
If the argument is one of no, false or 0, ParaStation will not start processes on these nodes.
It might be useful to prohibit the start of processes on a frontend machine since usually this machine is
reserved for interactive work done by the users. If the execution of processes is forbidden on a distinct
node, parallel tasks might be started from this node anyhow.
The default is to allow all nodes to run processes of parallel tasks.