Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

working directory as a job option #5

Closed
GoogleCodeExporter opened this issue Jul 24, 2015 · 2 comments
Closed

working directory as a job option #5

GoogleCodeExporter opened this issue Jul 24, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

My name is Shengqiang Shu, working with David Goodstein in JGI.

I have not found an option to pass in the working directory for a job. The 
reason is that NFS is slow and I want to use the farm node local disk as 
temporary working directory instead of 'configured working directory'.

If this option is not implemented, can we expect this will be implemented?

Thanks.


S. Shu

Original issue reported on code.google.com by sqs1...@gmail.com on 14 Sep 2011 at 10:11

@GoogleCodeExporter
Copy link
Author

Hi Shengqiang,

Please accept my apologies for not replying sooner.  We had not realised that 
users were using the Google-code issues tracker until recently and so are going 
through the issues on this list now.  The correct support email address for 
issues with InterProScan 5 is: support@ebi.ac.uk.

The option to set the working directory as a command line switch is implemented 
in release candidate 2.  Add the switch --tempdirname [path] OR -td [path] to 
the command line when running the interproscan.sh script.

best regards,

Phil Jones, InterPro Team, EMBL-EBI.

Original comment by philip.j...@gmail.com on 21 Aug 2012 at 3:14

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author

Original comment by Maxim.Sc...@gmail.com on 15 Aug 2013 at 11:21

  • Added labels: Subject-CommandLineOptions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant