Thanks for your response. Specifying -q queue@host doesn't achieve what
I'm looking to do. In my case, I'm trying to set up a drmaa runner that
will send the job to a torque host that is different from the one that is
set in /var/spool/torque/server_name on the client host. Configuring the
drmaa runner with -q queue@host doesn't do this for me. It still sends the
job to the torque host specified in /var/spool/torque/server_name.
Any other suggestions?
On Wed, Jun 26, 2013 at 4:06 PM, Adam Brenner <aebrenne(a)uci.edu> wrote:
I believe drmaa://-q somehost@queue-name
will work. However I could be very wrong. It has been a while since I
messed with the actual drmaa runners.
Computer Science, Undergraduate Student
Donald Bren School of Information and Computer Sciences
Research Computing Support
Office of Information Technology
University of California, Irvine
On Wed, Jun 26, 2013 at 1:28 PM, Bart Gottschalk <bgottsch(a)umn.edu> wrote:
> Is it possible to specify the torque host as part of a DRMAA runner URL?
> haven't been able to find a native_options parameter to allow for this.
> using the old style cluster configuration.
> Also, I haven't been able to find a list of native_options anywhere.
> such a list exist? If so, where?
> Please keep all replies on the list by using "reply all"
> in your mail client. To manage your subscriptions to this
> and other Galaxy lists, please use the interface at:
> To search Galaxy mailing lists use the unified search at: