# Default-log-dir not honored when running suricata command in foreground without -l parameter

**URL:** <https://forum.suricata.io/t/default-log-dir-not-honored-when-running-suricata-command-in-foreground-without-l-parameter/5332>\
**Category:** Help\
**Created:** [February 3, 2025, 11:50pm UTC](https://forum.suricata.io/t/default-log-dir-not-honored-when-running-suricata-command-in-foreground-without-l-parameter/5332 "2025-02-03T23:50:53Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Osqui](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.suricata.io/osqui/32/2909_2.png) [@Osqui](https://forum.suricata.io/u/Osqui)\
**Post date:** [February 3, 2025, 11:50pm UTC](https://forum.suricata.io/t/default-log-dir-not-honored-when-running-suricata-command-in-foreground-without-l-parameter/5332/1 "2025-02-03T23:50:53Z")

</div>

> Please include the following information with your help request:
> 
> - Suricata version → Suricata 7.0.3
> - Operating system and/or Linux distribution → Ubuntu 24.04.1
> - How you installed Suricata (from source, packages, something else): sudo apt install suricata

When running sudo suricata -c /etc/suricata/suricata.yaml -r some.pcap I’ve noticed fast.log, eve.json and stats.log files are created in current working directory instead of in /var/log/suricata directory, which is the location set inside suricata.yaml config file (specifically, in its default-log-dir: option). I must add -l /var/log/suricata argument in order to put these files inside this wanted folder.

That’s not the documented behaviour, so I infer there’s some bug.  
Thanks

---

<div class="post-metadata">

**Author:** ![Jeff\_Lucovsky](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.suricata.io/jeff_lucovsky/32/11_2.png) [@Jeff\_Lucovsky](https://forum.suricata.io/u/Jeff_Lucovsky)\
**Post date:** [February 5, 2025, 2:40pm UTC](https://forum.suricata.io/t/default-log-dir-not-honored-when-running-suricata-command-in-foreground-without-l-parameter/5332/2 "2025-02-05T14:40:25Z")

</div>

Thanks for reaching out.

I’ve looked at the source code and the behavior is intentional, even if not documented.

---

<div class="post-metadata">

**Author:** ![ish](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.suricata.io/ish/32/8_2.png) [@ish](https://forum.suricata.io/u/ish)\
**Post date:** [February 5, 2025, 3:28pm UTC](https://forum.suricata.io/t/default-log-dir-not-honored-when-running-suricata-command-in-foreground-without-l-parameter/5332/3 "2025-02-05T15:28:02Z")

</div>

The idea behind this is if Suricata is also running as a service, and you run it as a PCAP and log to the same directory, you will corrupt those log files for the service.

So running on a device is considered system mode, and on a file is user mode, where as you noticed logs to current directory.

Yes, we need documentation on this.

---

<div class="post-metadata">

**Author:** ![jufajardini](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.suricata.io/jufajardini/32/896_2.png) [@jufajardini](https://forum.suricata.io/u/jufajardini)\
**Post date:** [February 5, 2025, 7:07pm UTC](https://forum.suricata.io/t/default-log-dir-not-honored-when-running-suricata-command-in-foreground-without-l-parameter/5332/4 "2025-02-05T19:07:35Z")

</div>

Indeed, there’s a ticket for that, even… [Documentation #7545: userguide: document user mode and system mode and their relation to the log directory - Suricata - Open Information Security Foundation](https://redmine.openinfosecfoundation.org/issues/7545)

---

<div class="post-metadata">

**Author:** ![Osqui](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.suricata.io/osqui/32/2909_2.png) [@Osqui](https://forum.suricata.io/u/Osqui)\
**Post date:** [February 6, 2025, 12:42pm UTC](https://forum.suricata.io/t/default-log-dir-not-honored-when-running-suricata-command-in-foreground-without-l-parameter/5332/5 "2025-02-06T12:42:22Z")

</div>

Thanks very much everyone!!
