# A question about the default user and a question for .tar package installed as system service

**URL:** <https://discuss.elastic.co/t/a-question-about-the-default-user-and-a-question-for-tar-package-installed-as-system-service/53872>\
**Category:** Elasticsearch\
**Created:** [June 24, 2016, 9:31am UTC](https://discuss.elastic.co/t/a-question-about-the-default-user-and-a-question-for-tar-package-installed-as-system-service/53872 "2016-06-24T09:31:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![yangfeiran](https://avatars.discourse-cdn.com/v4/letter/y/7ea924/32.png) [@yangfeiran](https://discuss.elastic.co/u/yangfeiran)\
**Post date:** [June 24, 2016, 9:31am UTC](https://discuss.elastic.co/t/a-question-about-the-default-user-and-a-question-for-tar-package-installed-as-system-service/53872/1 "2016-06-24T09:31:00Z")

</div>

Hello community,

Here I have two questions:

A question about the default user:  
As we know, after install the elasticsearch by RPM, we will have a default user (which is elasticsearch) automatically. But sometimes we want to use another name for the elasticsearch. It is because sometimes we have different companies using single machine. If we have different user, we can identify whose elasticsearch it is. How can we do that?

Second, after I installed the Elasticsearch RPM package, Elasticsearch can be started and stopped as system service, using command like ' service elasticsearch start' and ' service elasticsearch stop'. Does the .tar package have the ability to be a system service? Or should we do something to the /etc/init.d/ directory to make it happen? To imitate the /etc/init.d/elasticsearch that RPM package created, so I can create a /etc/init.d/elasticsearch file in the .tar way? By the way, I have tried to just change the path of the Es parameter like this,ES\_HOME="/opt/elasticsearch-2.1.1"  
MAX\_OPEN\_FILES=65535  
MAX\_MAP\_COUNT=262144  
LOG\_DIR="/data/elasticsearch2.1/log"  
DATA\_DIR="/data/elasticsearch2.1/data"  
CONF\_DIR="/opt/elasticsearch-2.1.1/config".  
And run the service, it says "elasticsearch (pid 20640) is running...", after several seconds, it says "elasticsearch dead but subsys locked".

I solved the second problem on my own. You need to delete the ES\_ENV\_FILE config. The first one remains a problem! Hopefully, someone can solve it.

Best wishes,

Feiran

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 25, 2016, 8:51pm UTC](https://discuss.elastic.co/t/a-question-about-the-default-user-and-a-question-for-tar-package-installed-as-system-service/53872/2 "2016-06-25T20:51:46Z")

</div>

This isn't something that ES can manage, you need to do it on the OS level.

The only native multitenancy option for ES would be to leverage Shield.

---

<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:** [July 5, 2017, 10:40pm UTC](https://discuss.elastic.co/t/a-question-about-the-default-user-and-a-question-for-tar-package-installed-as-system-service/53872/3 "2017-07-05T22:40:30Z")

</div>


