# Installation questions regarding systemd

**URL:** https://discuss.elastic.co/t/installation-questions-regarding-systemd/162265
**Category:** Elasticsearch
**Created:** [December 27, 2018, 4:42pm UTC](https://discuss.elastic.co/t/installation-questions-regarding-systemd/162265 "2018-12-27T16:42:12Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![swright-eti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/swright-eti/32/38743_2.png) [@swright-eti](https://discuss.elastic.co/u/swright-eti)
#### Post date: [December 27, 2018, 4:42pm UTC](https://discuss.elastic.co/t/installation-questions-regarding-systemd/162265/1 "2018-12-27T16:42:12Z")

</div>

It looks like ElasticSearch, LogStash, and Kibana RPMs put systemd files in different places. Why is that?  
I did a deploy of all 3 on a fresh VM. I expected all three files to be in the same place, but ElasticSearch puts its file in /usr/lib/systemd/system/elasticsearch.service

```
[root@elk elasticsearch]# ls /etc/systemd/system/logstash.service 
/etc/systemd/system/logstash.service
[root@elk elasticsearch]# ls /etc/systemd/system/kibana.service 
/etc/systemd/system/kibana.service
[root@elk elasticsearch]# ls /etc/systemd/system/elasticsearch.service
ls: cannot access /etc/systemd/system/elasticsearch.service: No such file or directory
[root@elk elasticsearch]# ls /usr/lib/systemd/system/elasticsearch.service 
/usr/lib/systemd/system/elasticsearch.service
[root@elk elasticsearch]#
```

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [January 24, 2019, 4:42pm UTC](https://discuss.elastic.co/t/installation-questions-regarding-systemd/162265/2 "2019-01-24T16:42:23Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.