Knime PATH does not match to system user PATH Variable

[mwiegand]

Update … As identified by @carstenhaubold in:

External Tool "issues" and high difficulty to use

Aaah . Learn something new every day they say… This seems to be a security feature of OSX. When a program is started normally, meaning by double clicking the application or calling it via Spotlight, the PATH variable is cleared out by OSX. However, if you start KNIME from a terminal, you can make it inherit the full environment like so: navigate into your KNIME application’s Contents/MacOS folder with the terminal, from your output above this seems to be /Applications/KNIME.app/…

The issue is caused by “security mechanisms” of OS X. In order to circumvent / expose the users PATH variable, knime must be started via command line by:

1. Navidating to the executabel via cd /Applications/KNIME.app/Contents/MacOS/
2. Start knime via ./knime

However, this comes with a not so insignificant disadvantage as the terminal must, under any circumstances, being kept open. If close by accident, knime is immediately stopped (not properly shut down).

Adding to this. the start up window seems to not list the loaded / installed extensions. However, they are still accessible (bug or feature?)

I’d like to propose to enable defining / overwriting the PATH variable manually in the External Nodes. Similar to how it was made possible by @AnotherFraudUser in AF Utilities (big thanks!)

External Tool "issues" and high difficulty to use

Hi @mwiegand, @iCFO, took a bit longer due to issues with the node deployment. But I added a script execution node to the AF Utilities which hopefully covers at least the basic usecases from the BASH node [grafik] I added env-prefs to maybe also cover @mwiegand problem where you can change or add new enviroment settings used by the node (by default it reads all enviroment settings which are used by default) [grafik] But have to say did not use the old bash node at all - so things could …

Reason is, the “security” measure might get in this or another way implemented by other OS vendors too. The struggle which many had to go through to identify the cause would be easily avoidable but also would allow to add a significant amount of flexibility in defining binaries.