Closed goetzk closed 3 years ago
change line 67 and 68 From: test "$VAR" || VAR=$(cd $curpath/../../var && pwd) test "$ETC" || ETC=$(cd $curpath/../../etc && pwd) To: test "$VAR" || VAR=$(cd $curpath/../../../var && pwd) test "$ETC" || ETC=$(cd $curpath/../../../etc && pwd)
SOLVED! Issue
The same init script is used on Debian systems, your fix will result in a broken init script on that platform. The correct fix depends a lot on why things are this way.
The change was made in commit 55bb897f43ef12647777717a0ba956e57e4d49ee , from which it is reasonable to assume it is supposed to decouple the directories from /usr/local/.
I suggest that the correct fix is one or both of:
I do not know if the solution that applies solve on debian systems since I use centos, but if I think you should use the option of systemd or make the configuration chkconfig as they say.
Or you can use script in directory for_fedora... Centos/EPEL and Fedora Init or Systemd script work fine.
2017-06-01 21:37 GMT+02:00 Victor Pereira notifications@github.com:
I do not know if the solution that applies solve on debian systems since I use centos, but if I think you should use the option of systemd or make the configuration chkconfig as they say.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/naparuba/shinken/issues/1901#issuecomment-305598358, or mute the thread https://github.com/notifications/unsubscribe-auth/AAwrYPPF94BGJIhRaZc-WQ4Ne5B2Bmq4ks5r_xMGgaJpZM4M-nLQ .
-- David Hannequin
@hvad do you think it would be feasible to install that init script / systemd unit on Centos by default?
@goetzk that i do on rpm package.
Hi, I had a quick look for existing issues so apologies if this has already been reported.
OS:
Shinken:
This is from a test run
It appears to be the result of init.d being a symlink.
The root cause appears to be in /etc/rc.d/init.d/shinken where it has
These paths are not defined yet when run via the arbiter, so /var and /etc/ cause errors. /bin/ succeeds by pure chance - the /bin has been left off the path so due to that bug there is no error in the test.