Hi all.<br><br>After a long time over this subject, I found the following:<br><br>###########<br><b>$ diagnose -c</b><br>Class/Queue Status<br><br>Name           Priority Flags        QDef              QOSList* PartitionList        Target Limits<br>
<br>qm                    0 [NONE]       [NONE]             [NONE]  [NONE]                0.00  [NONE]  DEFAULT.FEATURES=[quantum]  <u>MAXJOBPERUSER=1,1</u><br>cluster               0 [NONE]       [NONE]             [NONE]  [NONE]                0.00  [NONE]  DEFAULT.FEATURES=[cluster]<br>
###########<br><br>As one can see, not only the &quot;cluster&quot; queue has absolutely NO limits, as there is a strange and non-defined limit for the &quot;qm&quot; queue. Do to that, and after trying different but similar syntaxes for CLASSCFG line, I gave up and did a workaround using USERCFG and GROUPCFG. Now, diagnosing for classes, users and groups yields me the following:<br>
<br>################<br><b>$ diagnose -c</b><br>Class/Queue Status<br><br>Name           Priority Flags        QDef              QOSList* PartitionList        Target Limits<br><br>qm                    0 [NONE]       [NONE]             [NONE]  [NONE]                0.00  [NONE]  DEFAULT.FEATURES=[quantum]  <u>MAXJOBPERUSER=1,1</u><br>
cluster               0 [NONE]       [NONE]             [NONE]  [NONE]                0.00  [NONE]  DEFAULT.FEATURES=[cluster]<br><br><b>$ diagnose -g</b><br>Displaying group information...<br>Name         Priority        Flags         QDef      QOSList*        PartitionList Target  Limits<br>
<br>DEFAULT             0       [NONE]       [NONE]       [NONE]                [NONE]   0.00  MAXPROC=16<br>group1                0       [NONE]       [NONE]       [NONE]                [NONE]   0.00  MAXPROC=16<br>group2              0       [NONE]       [NONE]       [NONE]                [NONE]   0.00  MAXPROC=16<br>
<br><b># diagnose -u</b><br>Displaying user information...<br>Name         Priority        Flags         QDef      QOSList*        PartitionList Target  Limits<br><br>DEFAULT             0       [NONE]       [NONE]       [NONE]                [NONE]   0.00  MAXPROC=8<br>
user1              0       [NONE]       [NONE]       [NONE]                [NONE]   0.00  MAXPROC=8<br>user2            0       [NONE]       [NONE]       [NONE]                [NONE]   0.00  MAXPROC=8<br>user3             0       [NONE]       [NONE]       [NONE]                [NONE]   0.00  MAXPROC=8<br>
...<br>###############<br><br>In this way, the queue &quot;cluster&quot; is now working and the queue limits are enforced. Since I heard from other maui users that they also got issues when trying to use CLASSCFG statements, and also have done similar workarounds, it really seems that there is a severe bug on this option.<br>
<br>Also, I&#39;m disturbed by the limitation in the &quot;qm&quot; queue. Since I&#39;m not  explicit ordering any limitation for that queue in the maui.cfg file anymore, and specially not limiting the max number of jobs per user, is there any other configuration file that I may have wrongly and inadvertidly set some sort of limitation on this specific queue?<br>
<br>Thanks,<br><br>Jones<br>