Hi, Am 18.04.2011 um 13:45 schrieb Vic:
> I've got a couple of issues with using holds. It's probably a user error, > but I can't work out what I need to do :-( > > The first problem is that I want to start a job in a held state. the qsub > man page says I can use the "-h" option to do this - but unfortunately, what options do you use in addition - it's a plain `qsub`? It should return instantly and you can also add -terse to the options to get a plain jobnumber as output. > this doesn't give me a job number, or even return until I release the > hold. Is there a way to submit the job as held, get the jobnum, do some > other stuff, then release the job? > > Secondly, I'm getting some permission problems with qalter. I can start a > job, set a user hold (with qhold), then try to resume with qalter. That > gives me the error of "must be manager to remove manager hold", even > though it's clearly a user hold (set up by the qhold command in the same > terminal). And you are not a manager on your own I assume. `qrls` yields the same result (although `qhold` and `qrls` use `qalter` in the end)? > Am I doing something truly stupid? > > The background to all this (in case anyone's interested) is that I have a > bunch of long-running jobs that depend on an executable being in > existence. My first job is a checkout/make operation that can take a > little while (hence the need to do it in the queue), but sometimes will be > complete in very short order. I'm trying to avoid the race between setting > off the first job, and setting the last job to depend on it... Maybe you could also submit the second job with -hold_jid and supply a jobname instead of a job number (it needs to be unique of course in this case). -- Reuti > Thanks! > > Vic. > > _______________________________________________ > users mailing list > [email protected] > https://gridengine.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
