Hi all, I have a couple of question about both commands.
>From maui admin guide: setspri can set absolute or relative priority to a job. a.) absolute priority sets a job priority higher than any calculated value. b.-) Maui calculated are in the range of 1 to 1 billion. The example: setspri PRIO JOBID will assign a priority of 1billion+PRIO to JOBID. That's not true in my system, it's setspri -r: ----------------------- ]# setspri 1 4945238 job system priority adjusted # checkjob 4945238 checking job 4945238 [...] PE: 1.00 StartPriority: -1436 SystemPriority: 1 -------------------------- But: --------------------------- # setspri -r 1 4945238 job system priority adjusted [r...@pbs02 ~]# checkjob 4945238 [...] PE: 1.00 StartPriority: -1436 SystemPriority: 2000000001 --------------------------- Other example: # checkjob 4962162|grep -i prio PE: 1.00 StartPriority: 1627 # diagnose -p |grep 4962162 4962162 1628 0.0( 0.0: 0.0: 0.0) 100.0( 0.0:776.0:851.9) Both commands shows different prio for same job, why? Anyway, I'd like to increase the prio until 2000: # setspri 2000 4962162 ERROR: system priority must be in the range 0 - 1000 So, with "absolute" prio I can go only till 1000? How may I set a prio of negative value o "reasonable" value? # checkjob 4962162|grep -i prio PE: 1.00 StartPriority: 1718 SystemPriority: 1000 but If I do: # setspri -r 100 4962162 job system priority adjusted [r...@pbs02 ~]# checkjob 4962162|grep -i prio PE: 1.00 StartPriority: 1000000100 SystemPriority: 2000000100 While diagnose keeps showing: # diagnose -p |grep 4962162 4962162 1623* 0.0( 0.0: 0.0: 0.0) 100.0( 0.0:775.5:847.7) Ok, wildcard means that the priority is going to change, but the new value is never shown. So, if setspri is only used to "force" a job to run, why two kind of setspri? Why a range of 1-1000? What am I missunderstanting? the whole concept? :-) TIA, Arnau _______________________________________________ mauiusers mailing list [email protected] http://www.supercluster.org/mailman/listinfo/mauiusers
