Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set kibana service to be Automatic and autostart it #5

Closed
angryhussord opened this issue Apr 14, 2017 · 3 comments
Closed

Set kibana service to be Automatic and autostart it #5

angryhussord opened this issue Apr 14, 2017 · 3 comments
Labels

Comments

@angryhussord
Copy link

In the spirit of Chocolatey, an apt-get style tool for package management and installation, I beg you to automatically set the startup type to automatic and then automatically start the service as well. The audience using Chocolatey doesn't need that choice. We want our software auto-installed and running without any hand edits or after-install configuration whenever possible.

@ChrisMagnuson
Copy link
Member

@angryhussord Sorry it has taken so long to get back to you.

If you look at the documentation for the rpm package and deb package of Kibana from elastic search they both do not start automatically after Kibana has been installed but leave that as a additional step for someone to perform if they want it automatically started.

My general experience with Arch linux and others has been that many server style applications default to creating the service but starting it or not setting it to start automatically.

Given that Elastic.co isn't currently starting the service via their other distribution means and it doesn't feel like it is a hard and fast rule or expectation that installed servers should automatically start I think it is better to have the kibana package configure a service but leave it set to manual and not automatic.

@ChrisMagnuson
Copy link
Member

As a counter example the maria db chocolatey package does start the MySQL service after the package is installed.

@ChrisMagnuson
Copy link
Member

Closing as there seems to be a precedent for the current behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants