Fix bug in Init/Shutdown scripts create and edit modes
I am currently working with this user interface and finding it .... extremely inconsistent.
Firstly, see this screenshot.
How can I have a 'script' command set and a 'command' command set?
I have been editing the same entry, each time I go to edit the entry, it seems to forget if it's a script or command, it forgets if it's post or pre.
I've tried a mammoth amount of combinations of commands (which I know work in the CLI when I SSH in)
Also, I know this command works in SSH, 100% - NONE of these 6 (!) entries are working for me.
Also, there's discussion in previous old forum threads about FreeNAS, discussing keeping script files in /data/ (yeah, presumably the FreeNAS root USB?)
When I attempt to replicate this, I can't point (in the new UI) to /data/ I have to do it off /mnt/ points.
I have set my script as +x and I've set a +777. I know the script runs in CLI, I can not in any way get the system to execute it.
Look at this command.
/mnt/ARRAY/media/33/FreeNAS-scripts-master/set_hdd_erc.sh | tee -a /mnt/ARRAY/media/bob.log
100% does what it is supposed to and writes a log file, won't work in the init section, no matter what I do.
I think the key thing here, in the very least is the fact entries 'forget' if they're command or script, they forget if they're pre or post.
Can someone please take a look
#1 Updated by Erin Clark over 1 year ago
- Subject changed from Init / Shutdown scripts UI seems to be inconsistent / odd. to Init / Shutdown scripts UI edit mode appears to be broken.
- Assignee changed from Release Council to Vaibhav Chauhan
- Target version changed from Backlog to 11.2-U2
BRB: There appears to be a bug with edit mode where it is not loading the saved values. VB will look into this.