Skip to content

Conversation

@henriquesimoes
Copy link

Most files have incorrect permission bits regarding execution. Clean this up by running:

find -type f -executable \
    -regex '.*\(pdf\|png\|doc\|txt\|html\|adl\|c\|h\|cpp\|dbd\|db\|substitutions\)$' \
    -exec chmod -x {} \;

Besides those, mcaApp/SISSrc/prom_v0111.mcs and Amptek' BMP files also had their execution removed.

Same thing for Windows and VxWorks iocsh scripts, since they should be provided as argument to the IOC binary on those systems, AFAIK; thus not requiring themselves to be executable.

For Unix scripts, add a shebang so they can be indeed properly executed.

Most files have incorrect permission bits regarding execution. Clean
this up by running:

$ find -type f -executable \
>    -regex '.*\(pdf\|png\|doc\|txt\|html\|adl\|c\|h\|cpp\|dbd\|db\|substitutions\)$' \
>    -exec chmod -x {} \;

Besides those, mcaApp/SISSrc/prom_v0111.mcs and Amptek' BMP files also
had their execution removed.
Windows and VxWorks iocsh scripts should be provided as argument to the
IOC binary on those systems. This means scripts themselves do not need
to be executable. Moreover, nfsCommands is loaded afterwards in VxWorks
scripts, and therefore also does not need to be executable.
These scripts had executable bits set, but none of them was actually
executable due to the missing shebang. Add proper shebangs so one can
ask the OS to actually run them directly.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant