Open EugeneOne1 opened 3 months ago
Both workarounds are quite suboptimal. Rescheduling to v0.1.0. Perhaps we'll figure something out by then.
As per a51b997a6e5f5212ebd0afbeaf9698385daaef7f, we've implemented logging to the system logger via the /usr/bin/logger
utility. This issue will remain open until the mentioned Go issue is resolved.
Prerequisites
[X] I have checked the Knowledge Base and the Discussions and found no answer
[X] I have searched other issues and found no duplicates
[X] I want to report a bug and not ask a question or ask for help
[X] I have set up AdGuard DNS Clients correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)
Platform (OS and CPU architecture)
Darwin (aka macOS), AMD64 (aka x86_64)
Installation
GitHub releases
Setup
On a personal machine
AdGuard DNS Client version
v0.0.1
Action
Without any configuration run:
Expected result
An error message in the Console app:
Actual result
No mentions of
AdGuardDNSClient
process.Additional information and/or screenshots
May be related to https://github.com/golang/go/issues/59229.