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 <E.Burkov@AdGuard.COM>
Date:   Mon Feb 28 16:13:25 2022 +0300

    FAQ: specify version

commit 3e0806e141b83ee9789592eb0835871356e9887b
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Mon Feb 28 16:09:08 2022 +0300

    FAQ: imp structure

commit 958d75a33e4d3e7e4d6002d928e005c0a63ac530
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Mon Feb 28 15:49:14 2022 +0300

    FAQ: freebsd and openbsd service log
Eugene Burkov 2022-02-28 16:26:55 +03:00
parent 1f0862924e
commit ef94d97979
1 changed files with 6 additions and 4 deletions

8
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` * **Linux** systems with **Snapcraft** use the `snap logs adguard-home`
command. command.
* **FreeBSD** and **OpenBSD:** currently, no logs are written by default. * **FreeBSD:** `/var/log/daemon.log` (**since v0.108.0-b.4**). Before
That will change in the future, see [issue 4213]. **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. * On **Windows:** the [Windows Event Log][wlog] is used.
[wlog]: https://docs.microsoft.com/en-us/windows/win32/wes/windows-event-log [wlog]: https://docs.microsoft.com/en-us/windows/win32/wes/windows-event-log
[issue 4213]: https://github.com/AdguardTeam/AdGuardHome/issues/4213