Bug 773378

Description of problem:
Limits are shown only after submitting job with concurrency_limits. And then they are shown even after job is finished and removed. After restarting condor they are gone again.

# grep _LIMIT /etc/condor/config.d/99sgraf.config
TEST_LIMIT = 1
ecode=0
# condor_config_val -dump | grep _LIMIT
TEST_LIMIT = 1
ecode=0
# service condor restart
Stopping Condor daemons:                                   [  OK  ]
Starting Condor daemons:                                   [  OK  ]
ecode=0

Look into cumin - Grid::Limits
And there is no limits.

# su - test -c 'echo -e "Executable = /bin/sleep\nOutput = /tmp/pokus\nUniverse = vanilla\nconcurrency_limits = TEST\nargs = 60\nqueue 1" | condor_submit'
Submitting job(s).
1 job(s) submitted to cluster 5.
ecode=0

Now you can see limit 'test' in cumin, with current usage '1.0'

After job quits, limit 'test' is still there with current usage '0.0'

This information should be in cumin from the beginning.

Now if you restart condor, information about limit is lost again. Until someone use it in submission.

Version-Release number of selected component (if applicable):
cumin-0.1.4916-1.el5.noarch (from RHN)

How reproducible:
100%

Steps to Reproduce:
1. Install condor+cumin
2. Set limit
3. Look into cumin (no limit)
4. Submit job using limit
5. Look into cumin (limit is there and does not disappear)
  
Actual results:
Information about limits is displayed from the first usage.

Expected results:
Information about limits is there from the beginning (starting condor).

Additional info: