From ef94d97979d4ecc5687ee4963ab048195c124f54 Mon Sep 17 00:00:00 2001 From: Eugene Burkov Date: Mon, 28 Feb 2022 16:26:55 +0300 Subject: [PATCH] Pull request: 4213 bsd syslog Merge in DNS/adguard-home-wiki from 4213-bsd-syslog to master Squashed commit of the following: commit 0f9db48fbb7a196e8398be19019c873f1969ac68 Author: Eugene Burkov Date: Mon Feb 28 16:13:25 2022 +0300 FAQ: specify version commit 3e0806e141b83ee9789592eb0835871356e9887b Author: Eugene Burkov Date: Mon Feb 28 16:09:08 2022 +0300 FAQ: imp structure commit 958d75a33e4d3e7e4d6002d928e005c0a63ac530 Author: Eugene Burkov Date: Mon Feb 28 15:49:14 2022 +0300 FAQ: freebsd and openbsd service log --- FAQ.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/FAQ.md b/FAQ.md index b48641a..f180346 100644 --- a/FAQ.md +++ b/FAQ.md @@ -92,13 +92,15 @@ logs) depends on the operating system and installation mode: * **Linux** systems with **Snapcraft** use the `snap logs adguard-home` command. - * **FreeBSD** and **OpenBSD:** currently, no logs are written by default. - That will change in the future, see [issue 4213]. + * **FreeBSD:** `/var/log/daemon.log` (**since v0.108.0-b.4**). Before + **v0.108.0-b.4** no logs are written by default. + + * **OpenBSD:** `/var/log/daemon` (**since v0.108.0-b.4**). Before + **v0.108.0-b.4** no logs are written by default. * On **Windows:** the [Windows Event Log][wlog] is used. -[wlog]: https://docs.microsoft.com/en-us/windows/win32/wes/windows-event-log -[issue 4213]: https://github.com/AdguardTeam/AdGuardHome/issues/4213 +[wlog]: https://docs.microsoft.com/en-us/windows/win32/wes/windows-event-log