Batch Submit Apps - eval vs execution of script.sh.erb

Get Help
1

We have gone live with 2 new apps in our openondemand instance. One passenger App and one Batch Submit App.

The Batch submit app gave us grief initially due to NOT having execution permissions set on the script.sh.erb (744) file in the template dir. We assumed that this would get evaluated by the app due to being wrapped in Ruby, however it appears it inherits the permissions of the original file.

Is there a way to dynamically change permissions on eval of the submit.sh.erb file? Or should we just assume executable permissions need to be universal for all just to be safe?

We have a workaround, (mode 755), we just want to understand what is happening and what is possible moving forward.

As always, thanks for your help!

2

I think you need at least 744.

The files need to be readable so that the user can copy them to their $HOME directory and executable because job_script_content.sh (the main wrapper script) will execute them.

3

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.