Hi Michael, I feel your pain. I have lots of such naive queries which are starting to hit their limits... ;) Cheers, Max > Am 07.05.2018 um 02:42 schrieb Michael Pelletier <Michael.V.Pelletier@xxxxxxxxxxxx>: > > Thanks for that, Max!! > > I had been using the following hack: > > /usr/bin/condor_status -constraint 'State == "Claimed" && !isUndefined(ConcurrencyLimits)' -format '%v' 'split(ConcurrencyLimits, ", ")' > > Yours is much more elegant, tight-knit, and scalable. I always forget to check the other daemons' ClassAds, let alone with condor_userprio. > > -Michael Pelletier. > > -----Original Message----- > From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx] On Behalf Of Fischer, Max (SCC) > Sent: Friday, May 4, 2018 8:48 AM > To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx> > Subject: [External] Re: [HTCondor-users] Get Concurrency Limit Usage > > Hi all, > > Turns out a condor_userprio query directed at the negotiator does the trick. > > A query such as > condor_userprio -negotiator -long | grep Limit works fine for our use case. > > Cheers, > Max > > _______________________________________________ > 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/
Attachment:
smime.p7s
Description: S/MIME cryptographic signature