David A. Wynne created NIFI-1709:
------------------------------------
Summary: The nifi.sh install script assumes RHEL directories
Key: NIFI-1709
URL: https://issues.apache.org/jira/browse/NIFI-1709
Project: Apache NiFi
Issue Type: Improvement
Components: Tools and Build
Environment: SUSE
Reporter: David A. Wynne
Priority: Minor
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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
