-
Notifications
You must be signed in to change notification settings - Fork 75
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
Provide a systemd flag for "vendor" vs admin #137
Comments
It’s unclear when I was initially reading systemd docs what these terms
(admin, vendor, etc) meant. In most docs I remember, the implication is
that the vendor is the upstream linux distro, so I chose /etc/ based on
this.
Can you help me understand the negative impact of the current location used
by pleaserun?
…On Wed, Dec 26, 2018 at 5:42 PM Josh Soref ***@***.***> wrote:
elastic/logstash appears to use pleaserun to generate its systemd service
(for ubuntu/debian).
Since logstash is being installed from a debian package made by the
vendor, the service should end up in /lib/systemd/system.
I saw a flag for -p systemd-user, it might make sense if there was a -p
systemd-packager.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#137>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAIC6kLMXG8-_Wjy9Hovd8dy4nJmROUAks5u9CV3gaJpZM4ZiOG8>
.
|
If I put something into It also means that I can quickly backup/copy the files that I've created to another system at any time w/o worrying about running into system packages or copying files that I shouldn't because they're owned by packages. Packages are supposed to go into |
https://www.digitalocean.com/community/tutorials/understanding-systemd-units-and-unit-files does a fairly good job of explaining the |
Probably the most important thing is that if you (a package manager) put a file in |
elastic/logstash appears to use pleaserun to generate its systemd service (for ubuntu/debian).
Since logstash is being installed from a debian package made by the vendor, the service should end up in
/lib/systemd/system
.I saw a flag for
-p systemd-user
, it might make sense if there was a-p systemd-packager
.The text was updated successfully, but these errors were encountered: