[
https://issues.apache.org/jira/browse/AIRAVATA-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260790#comment-13260790
]
Suresh Marru commented on AIRAVATA-365:
---------------------------------------
I don't think this is a good idea. On compute resources, /home is under quota
and if you fill it bo further jobs will run. So forcing users to explicitly
finding the scratch location and adding it is worth the pain. You can smarter
things like, if host is localhost, then set this to /tmp. I vote of leaving the
temporary location to blank, giving a chance for the user to think and type.
> Creating temporary location based on the given executable location
> ------------------------------------------------------------------
>
> Key: AIRAVATA-365
> URL: https://issues.apache.org/jira/browse/AIRAVATA-365
> Project: Airavata
> Issue Type: New Feature
> Components: XBaya
> Environment: mac
> Reporter: Lahiru Gunathilake
> Assignee: Saminda Wijeratne
> Fix For: 0.4-INCUBATING
>
>
> To make life easier for the user we need to derive the temporary location
> from the executable path and automatically fill it in to the input field. So
> if user want to change it user can do that.
> Ex: if user give the executable path as /home/lahiru/executable/echo.sh
> We can configure the temporary location to :
> /home/lahiru/execubale/workflow_runs
> Lahiru
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
