# Accès concurrentiel Filebeat sur disque local **URL:** \ **Category:** Discussions en français\ **Created:** [August 4, 2020, 11:08am UTC](https://discuss.elastic.co/t/acces-concurrentiel-filebeat-sur-disque-local/243692 "2020-08-04T11:08:40Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![LomigFR](https://avatars.discourse-cdn.com/v4/letter/l/dbc845/32.png) [@LomigFR](https://discuss.elastic.co/u/LomigFR)\ **Post date:** [August 6, 2020, 4:07pm UTC](https://discuss.elastic.co/t/acces-concurrentiel-filebeat-sur-disque-local/243692/3 "2020-08-06T16:07:12Z")
Bonjour, A tout hasard, si ça peut servir à quelqu'un, j'ai posté ma solution ici : > [@Competitive Filebeat access on local disk](https://discuss.elastic.co/t/competitive-filebeat-access-on-local-disk/243708/4): > > Hi, In fact, after some research of my own, I have resolved the concern in question. As you specify in your answer, the original problem is related to the (non-permitted) sharing of the /var/lib/filebeat-data directory. So here are the changes made in the two filebeat files. With this, I have two Filebeat components that work in separate namespaces (one harvests Nginx logs and the other harvests Apache logs). See the added and modified lines below. filebeat.yaml (namespace\_a): --- apiVersion:… Bonne lecture. --- _[View the full topic](https://discuss.elastic.co/t/acces-concurrentiel-filebeat-sur-disque-local/243692)._