Clarify GrpNodes configuration parameter use

Note that each job's node allocation is counted separately.
bug 548

doc/html/accounting.shtml

@@ -692,6 +692,9 @@ in the <a href="resource_limits.html">Resource Limits</a> document.</p>
   time from jobs running from this association and its children.  If
   this limit is reached new jobs will be queued but only allowed to
   run after resources have been relinquished from this group.
+  Each job's node allocation is counted separately
+  (i.e. if a single node has resources allocated to two jobs, this is counted
+  as two allocated nodes).
 </li>
 
 <li><b>GrpSubmitJobs=</b> The total number of jobs able to be submitted

doc/html/qos.shtml

@@ -109,6 +109,9 @@ allowed to run after resources have been relinquished from this group.
 The total count of nodes able to be used at any given time from jobs
 running from this QOS.  If this limit is reached new jobs will be queued
 but only allowed to run after resources have been relinquished from this group.
+Each job's node allocation is counted separately
+(i.e. if a single node has resources allocated to two jobs, this is counted
+as two allocated nodes).
 </li>
 
 <li><b>GrpSubmitJobs</b>

doc/html/resource_limits.shtml

@@ -145,6 +145,9 @@ specified then no limit will apply.</p>
   time from jobs running from this association and its children.  If
   this limit is reached new jobs will be queued but only allowed to
   run after resources have been relinquished from this group.
+  Each job's node allocation is counted separately
+  (i.e. if a single node has resources allocated to two jobs, this is counted
+  as two allocated nodes).
 </li>
 
 <li><b>GrpSubmitJobs=</b> The total number of jobs able to be submitted

doc/man/man1/sacctmgr.1

@@ -308,6 +308,9 @@ Resource plugin.
 Maximum number of nodes running jobs are able to be allocated in aggregate for
 this association and all associations which are children of this association.
 To clear a previously set value use the modify command with a new value of \-1.
+Each job's node allocation is counted separately
+(i.e. if a single node has resources allocated to two jobs, this is counted
+as two allocated nodes).
 
 .TP
 \fIGrpSubmitJobs\fP=<max jobs>
@@ -594,6 +597,9 @@ this association and all associations which are children of this association.
 \fIGrpNodes\fP
 Maximum number of nodes running jobs are able to be allocated in aggregate for
 this association and all associations which are children of this association.
+Each job's node allocation is counted separately
+(i.e. if a single node has resources allocated to two jobs, this is counted
+as two allocated nodes).
 
 .TP
 \fIGrpSubmitJobs\fP
@@ -1001,6 +1007,9 @@ Maximum number of running jobs in aggregate for this QOS.
 \fIGrpNodes\fP
 Maximum number of nodes running jobs are able to be allocated in aggregate for
 this QOS.
+Each job's node allocation is counted separately
+(i.e. if a single node has resources allocated to two jobs, this is counted
+as two allocated nodes).
 
 .TP
 \fIGrpSubmitJobs\fP
@@ -1132,6 +1141,9 @@ To clear a previously set value use the modify command with a new value of \-1.
 Maximum number of nodes running jobs are able to be allocated in aggregate for
 this QOS.
 To clear a previously set value use the modify command with a new value of \-1.
+Each job's node allocation is counted separately
+(i.e. if a single node has resources allocated to two jobs, this is counted
+as two allocated nodes).
 
 .TP
 \fIGrpSubmitJobs\fP
@@ -1483,6 +1495,9 @@ association and all associations which are children of this association.
 Maximum number of nodes running jobs are able to be
 allocated in aggregate for this association and all associations which
 are children of this association.
+Each job's node allocation is counted separately
+(i.e. if a single node has resources allocated to two jobs, this is counted
+as two allocated nodes).
 .TP
 \fIGrpSubmitJobs=\fP
 Maximum number of jobs which can be in a pending or
@@ -1559,6 +1574,9 @@ association and all associations which are children of this association.
 Maximum number of nodes running jobs are able to be
 allocated in aggregate for this association and all associations which
 are children of this association.
+Each job's node allocation is counted separately
+(i.e. if a single node has resources allocated to two jobs, this is counted
+as two allocated nodes).
 .TP
 \fIGrpSubmitJobs=\fP
 Maximum number of jobs which can be in a pending or