Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: 0.9.12
-
Fix Version/s: None
-
Component/s: Chef Client, Chef Server
-
Labels:None
-
Environment:
CentOS 5.5
Description
I had to build my own ruby in /usr/local. When installing the chef gems, all of the chef executables are created in /usr/local/bin.
The bootstart_client and bootstrap_server recipes symlinks everything over to /usr/sbin (assuming you have /usr/local/bin on your PATH)
However, the processes will fail to start because the intit scripts in the chef gem refer to /usr/bin/$executable, not /usr/sbin/$executable.
Updating the init scripts to use /usr/sbin will actually take advantage of the created symlinks, and make it easier to install chef in a less than standard location.
Issue Links
- duplicates
-
COOK-886
chef-server install on centos states /usr/sbin in some places and /usr/bin in others (and sysconfig file is being overridden... should be removed)
-
This isn't just an issue on CentOS, it is an issue on Ubuntu as well.