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.

Sign up for GitHub

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

Jump to bottom

service files belong in /lib/systemd/system not /etc/systemd/system #27768

Closed
jsoref opened this issue Dec 25, 2018 · 1 comment · Fixed by #83571
Closed

service files belong in /lib/systemd/system not /etc/systemd/system #27768

jsoref opened this issue Dec 25, 2018 · 1 comment · Fixed by #83571
Labels
bug Fixes for quality problems that affect the customer experience Feature:Build Packaging Team:Operations Team label for Operations Team

Comments

@jsoref
Copy link
Contributor

jsoref commented Dec 25, 2018

Kibana version:
6.5.4

Server OS version:
debian stretch 9.6

Original install method (e.g. download page, yum, from source, etc.):
apt http://artifacts.elastic.co/packages/6.x/apt

Describe the bug:
https://unix.stackexchange.com/questions/206315/whats-the-difference-between-usr-lib-systemd-system-and-etc-systemd-system

Steps to reproduce:

  1. install kibana (or the others), or look at the packaging: https://github.com/elastic/kibana/blob/94d99d63f3157d4a08eea83aa2489158b66a5e87/src/dev/build/tasks/os_packages/service_templates/systemd/etc/systemd/system/kibana.service

Expected behavior:
service files should live in /lib/systemd/system
Files that go in /etc/systemd/system should be placed by an admin manually (e.g. to override a package or because a package doesn't provide one).

I may provide a PR for this.

I hit it while trying to decide which files I needed to manually migrate when migrating an install
@sebelga sebelga added the Team:Operations Team label for Operations Team label Dec 25, 2018
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-operations

jsoref added a commit to jsoref/kibana that referenced this issue Dec 27, 2018
@jsoref
Switch from admin systemd location to vendor (elastic#27768)
6f73da4
@jsoref jsoref mentioned this issue Dec 27, 2018
Closed
7 tasks
@tylersmalley tylersmalley added Feature:Build Packaging bug Fixes for quality problems that affect the customer experience labels Mar 26, 2020
jbudz added a commit to jbudz/kibana that referenced this issue Nov 17, 2020
@jbudz
[deb/rpm] Move systemd service to /usr/lib/systemd/system
7e42d22 
Generally packages should install service files to
/usr/lib/systemd/system.  The current location is typically used for
services configured by the system maintainer.

Closes elastic#16046
Closes elastic#27768
@jbudz jbudz mentioned this issue Nov 17, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Fixes for quality problems that affect the customer experience Feature:Build Packaging Team:Operations Team label for Operations Team
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[deb/rpm] Move systemd service to /usr/lib/systemd/system jbudz/kibana
4 participants
@tylersmalley @jsoref @sebelga @elasticmachine