On 6/4/2015 4:49 PM, Iain Bradford Steers wrote:
Even after a restart of the central manager daemons, condor_userprio
still seems to put that user's job into <none>rather than the
group_u_OPS group(which doesn't get shown by userprio).
Anyone got any suggestions for how to sort this behaviour/reset the
limit?
Ugh...
Work-around suggestion to try:
Lets say the accounting principle is for instance
"group_foo.tannenba@xxxxxxxx". To get the group_foo to show up in
userprio with tannenba's jobs, I'd try the following on your central
manager (or any other machine with htcondor admin authorization):
condor_userprio -delete "group_foo.tannenba@xxxxxxxx"
condor_restart -negotiator
I think (hope) that will get you where you want to be. You will
unfortunately lose the historical accounting information associated
with group_foo.tannenba@xxxxxxxx, hopefully that is not important to
you in this instance.
Let me know if it works for you. We could/should handle this
situation better...
regards,
Todd
_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx
with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/