Do not start packages on installation #4256
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| @@ -46,9 +54,23 @@ The last command should verify a successful installation of the Oracle JDK. | |||
|
|
|||
| ==== RedHat/Centos/Fedora | |||
There was a problem hiding this comment.
Simple rule: It is always "Red Hat", never "RedHat". Always two words and capitalized.
See http://www.redhat.com/f/pdf/corp/trademark_usage.pdf
|
I will definitely walk though this with someone who is more into RHEL/Fedora spec files on our side than I am. Thanks a lot! |
|
👍 |
The reason to not start packages on installation is to allow to configure them before starting up (setting heap, cluster.name etc) Also the documentation was updated in order to show, which statements need to be executed. In addition, these statements are also printed out when the package is installed, depending on whether chkconfig, system or update-rc.d is used. Closes elastic#3722
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The reason to not start packages on installation is to allow to configure
them before starting up (setting heap, cluster.name etc)
Also the documentation was updated in order to show, which statements need
to be executed to start up elasticsearch and configure it to fire up automatically on boot.
In addition, these statements are also printed out when the package is
installed, depending on whether chkconfig, system or update-rc.d is used.
Closes #3722