[NIFI-1709] The nifi.sh install script assumes RHEL directories

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.3.0
• Component/s: Tools and Build
• Environment: SUSE
• Assignee: Andre F de Miranda
• Reporter: Wynner
• Created: 31/Mar/16 15:10
• Updated: 02/Jun/17 22:14
• Resolved: 02/Jun/17 22:14

Description

When setting up NiFi, the command:
bin/nifi.sh install

The following error occurs:
ln: failed to create symbolic link `/etc/rc2.d/S65nifi': No such file or directory
ln: failed to create symbolic link `/etc/rc2.d/K65nifi': No such file or directory
Service nifi installed

Looking in the nifi.sh, around line 145 - 148, you see:
rm -f "/etc/rc2.d/S65${SVC_NAME}"
ln -s "/etc/init.d/${SVC_NAME}" "/etc/rc2.d/S65${SVC_NAME}"
rm -f "/etc/rc2.d/K65${SVC_NAME}"
ln -s "/etc/init.d/${SVC_NAME}" "/etc/rc2.d/K65${SVC_NAME}"

It tries to symlink from /etc/init.d/nifi to /etc/rc2.d/S65nifi (and K65nifi).

The problem is that the script assumes that /etc/rc2.d exists in a SUSE system, which it doesn't.
In Suse11, this directory is /etc/init.d/rc2.d/

The script, especially the "install" option should correctly identify the OS flavor it runs on, and install the files in the correct location.

The next version of RHEL (8, not out yet), and Ubuntu 16.02 LTS (releasing next month), will use systemD, which does not have the concept of /etc/rc2.d directories, but works with "targets". The script will not be compatible with these OS changes.

Issue Links

• is duplicated by: NIFI-1715 NiFi install script does not support SUSE for service definitions
• links to: GitHub Pull Request #1794