Resource "Limit:<username>_setname_<limitcount>" remains in system forever, how to make it expire after certain # of days?

Fazel_Noor

When you submit a job with  -set  SETNAME  -limit SETNAME 30  , it gives it a limit of 30 jobs for that set before jobs 31 and over are queued.

In the resources, now there is a   Limit:<username>_SETNAME_30  created,  but this resource stays in the system indefinitely.

If you are creating a resource manually using the button at the bottom of the resource page (Add a new resource), the interface allows you to provide an expiry period (2d , 4h,  etc.) after which the resource will disappear.  But when the resource is created automatically like done above with the use of -set and -limit command line arguments, the resource stays valid indefinitely and has to manually be 'forget':  (vovresourcemgr forget Limit:... )

I have tried adding a random  -expire 2d  command argument after the -limit argument  (hoping the -expire option would do that, a shot in the dark kind of a thing) but obviously that didn't work.  But I am hoping someone can tell us how we can set a expiry for this resource as it is created.

 

 

 

 

Cary Wei

From what I understand, the answer is no, we don't have what you were looking for because it's created on the fly. What can be done is to run a vovcron/liveness that runs “vovforget -oldlimits” on a daily basis. This was what other customers had done and it worked well.

Fazel_Noor

Thank you Cary for your reply. We will try the vovforget -oldlimits and report back if any issues.