You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Customer reports that the default ncpa.cfg file on Ubuntu systems doesn't handle the setup of Python correctly. The NLS plugin in question is shebang'ed to use /bin/bash, whereas /bin/sh is symlinked on Ubuntu to /bin/dash. switchinf the ncpa.cfg for .sh files to use the bash command results in success.
Since shell scripts are normally shebang'ed (as the NLS script is) to use their shell of choice, do we even need to have the ,sh handler in ncpa.cfg?
The text was updated successfully, but these errors were encountered:
ne-bbahn
changed the title
FR - Default to shebang-specified shell instead of default extension execution for plugins
FR - Default to shebang-specified interpreter instead of default extension execution for plugins
Oct 8, 2024
From this Forum Post https://support.nagios.com/forum/viewtopic.php?t=75785
Customer reports that the default ncpa.cfg file on Ubuntu systems doesn't handle the setup of Python correctly. The NLS plugin in question is shebang'ed to use /bin/bash, whereas /bin/sh is symlinked on Ubuntu to /bin/dash. switchinf the ncpa.cfg for .sh files to use the bash command results in success.
Since shell scripts are normally shebang'ed (as the NLS script is) to use their shell of choice, do we even need to have the ,sh handler in ncpa.cfg?
The text was updated successfully, but these errors were encountered: