It's actually pretty simple. Assuming you save the script under the /ifs filesystem, you'll never be able to run it directly with ./ifs/scriptname.sh . Why? Because /ifs is mounted with noexec, but running it with simply /bin/zsh /ifs/scriptname.sh works just fine and you can put it in cron that way if you want. Just be aware that that cron jobs on Isilon are a bit different. They have to be put into /etc/local/crontab.local .
isilon3-1# mount | grep /ifs
OneFS on /ifs (efs, local, noatime, noexec)
------------------------------- A quick example:-------------------
crklosterman
450 Posts
0
March 19th, 2018 08:00
It's actually pretty simple. Assuming you save the script under the /ifs filesystem, you'll never be able to run it directly with ./ifs/scriptname.sh . Why? Because /ifs is mounted with noexec, but running it with simply /bin/zsh /ifs/scriptname.sh works just fine and you can put it in cron that way if you want. Just be aware that that cron jobs on Isilon are a bit different. They have to be put into /etc/local/crontab.local .
isilon3-1# mount | grep /ifs
OneFS on /ifs (efs, local, noatime, noexec)
------------------------------- A quick example:-------------------
isilon3-1# echo "isi_for_array uptime" >> /ifs/uptimescript.sh
isilon3-1# /bin/zsh /ifs/uptimescript.sh
isilon3-1: 4:55PM up 4 days, 1:55, 1 user, load averages: 0.47, 0.40, 0.34
isilon3-2: 4:55PM up 4 days, 7:12, 0 users, load averages: 0.37, 0.40, 0.34
isilon3-3: 4:55PM up 55 days, 22:42, 0 users, load averages: 0.39, 0.39, 0.38
Make Sense?
~Chris Klosterman
Principal Pre-Sales Engineer, Datadobi
StormyB
1 Rookie
•
10 Posts
0
March 19th, 2018 10:00
Hello Chris,
Thanks for the reply…
OK I can do it this way… It is to go in a scheduler named Control M…
I just thought that I could put the zsh in a script without having to call it preface it with zsh…
Thanks for the clarification,
MB