Apparently, it is a PATH problem. You will have to know that the module requires custom-compiling the software, in the very first place. If you haven’t gone through it, then you would have to do it immediately.

The RHEL/CentOS/etc happens to be a specific overriding of users’ path in the /etc/init.d file that sets to sbin:/usr/sbin:/usr/bin. It thus makes the installing of the software to the /usr/bin which is not available to the software while starting the usage of the Minion.The 2014.1.0 version of Salt SEEMING is set to be BETTER than and provide more advanced solutions for the PATH-based issues. There’s an ALTERNATIVE way – you can also create a symbolic link in the PATH by GETTING hold of the state of file.symlink.

1. –/usr/bin/foo:
2. – file.symlink:
3. –target: /usr_local/bin/foo.

Apparently, it is a PATH problem. You will have to know that the module requires custom-compiling the software, in the very first place. If you haven’t gone through it, then you would have to do it immediately.

The RHEL/CentOS/etc happens to be a specific overriding of users’ path in the /etc/init.d file that sets to sbin:/usr/sbin:/usr/bin. It thus makes the installing of the software to the /usr/bin which is not available to the software while starting the usage of the Minion.The 2014.1.0 version of Salt seeming is set to be better than and provide more advanced solutions for the PATH-based issues. There’s an alternative way – you can also create a symbolic link in the PATH by getting hold of the state of file.symlink.