Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Condor-users] How to make condor_userprio changes "stick"
- Date: Tue, 8 Mar 2005 17:57:44 -0500
- From: "Ian Chesal" <ICHESAL@xxxxxxxxxx>
- Subject: [Condor-users] How to make condor_userprio changes "stick"
Right now if I change the user priorities of my active users using the
condor_userprio -setprio command, on the next negotiation cycle the
priorities are reset to the condor-calculated values. How can I make my
forced settings stick? As an example, I force all my user priorities
into the following slightly ridiculous configuration:
[root@ttc-condorsrv log]# condor_userprio
Last Priority Update: 3/8 17:38
Effective
User Name Priority
------------------------------ ---------
ichesal@xxxxxxxxxx 0.50
bchan@xxxxxxxxxx 0.50
tvanderh@xxxxxxxxxx 0.50
jslavkin@xxxxxxxxxx 0.50
PYFU@xxxxxxxxxx 0.50
aling@xxxxxxxxxx 0.50
kbrunham@xxxxxxxxxx 3.00
clam@xxxxxxxxxx 16.91
kechan@xxxxxxxxxx 50.00
kschabas@xxxxxxxxxx 5000.00
jlaban@xxxxxxxxxx 500000.00
vmanohar@xxxxxxxxxx 50000000.00
rtessier@xxxxxxxxxx 5000000000.00
pguzy@xxxxxxxxxx 499999997952.00
hhoang@xxxxxxxxxx 50000000188416.00
dcashman@xxxxxxxxxx 5000000136282112.00
------------------------------ ---------
Number of users shown: 16
But two minutes later, when a negotiation cycle starts, everything is
reset to the condor-calculated values:
[root@ttc-condorsrv log]# condor_userprio
Last Priority Update: 3/8 17:40
Effective
User Name Priority
------------------------------ ---------
ichesal@xxxxxxxxxx 0.50
PYFU@xxxxxxxxxx 0.50
hhoang@xxxxxxxxxx 0.50
rtessier@xxxxxxxxxx 0.50
aling@xxxxxxxxxx 0.50
vmanohar@xxxxxxxxxx 0.63
dcashman@xxxxxxxxxx 2.24
kbrunham@xxxxxxxxxx 3.00
pguzy@xxxxxxxxxx 3.71
kechan@xxxxxxxxxx 12.01
kschabas@xxxxxxxxxx 13.64
jslavkin@xxxxxxxxxx 17.47
bchan@xxxxxxxxxx 19.35
tvanderh@xxxxxxxxxx 19.59
clam@xxxxxxxxxx 23.57
jlaban@xxxxxxxxxx 47.05
------------------------------ ---------
Number of users shown: 16
I've tried setting PRIORITY_FACTOR to be really big but that didn't make
a difference.
- Ian