# Control of ES log directory

**URL:** <https://discuss.elastic.co/t/control-of-es-log-directory/212975>\
**Category:** Elasticsearch\
**Created:** [December 24, 2019, 5:34pm UTC](https://discuss.elastic.co/t/control-of-es-log-directory/212975 "2019-12-24T17:34:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Thomas\_Doman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thomas_doman/32/11409_2.png) [@Thomas\_Doman](https://discuss.elastic.co/u/Thomas_Doman)\
**Post date:** [December 24, 2019, 5:34pm UTC](https://discuss.elastic.co/t/control-of-es-log-directory/212975/1 "2019-12-24T17:34:25Z")

</div>

ES: 6.1.1  
OS: Windows 10.0.14393

I have set up our `elasticsearch.yml` file, as shown below, to direct logging to a different drive than the C: drive where the executable runs. However, I still see `stdout` and `stderr` being logged to the C: drive. Why? Is there a way to control this? There **are** logs going to the Q: (ie. the main logs and slow search and indexing logs) so I'm not sure why they don't **all** go to the specified location.

```
path:
data: Q:\Elasticsearch\data
logs: Q:\logs
```

---

<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 21, 2020, 5:38pm UTC](https://discuss.elastic.co/t/control-of-es-log-directory/212975/2 "2020-01-21T17:38:00Z")

</div>

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