Closed xenophon61 closed 1 month ago
Addendum
In order for the change outlined above to survive reboots or issuing a "sudo brew services restart znapzend", one must
Test by restarting the brew service. It should be fine.
~ % sudo launchctl list | grep znap 41833 0 homebrew.mxcl.znapzend
Hi, and thanks for a great resource!
This issue applies to a fresh Homebrew install in macOS Sonoma (had been using the GitHub releases up until now, but it's so much simpler with $brew install znapzend). More specifically, the znapzend daemon (in effect a Launchctl service) is not initialized properly, giving the following error:
% sudo launchctl list | grep znap 22054 2 homebrew.mxcl.znapzend
% sudo launchctl error 2 2: No such file or directory
The fix is rather easy:
sudo brew services start znapzend
`
Hope this helps. Not sure where to post this, but opted to let oetiker know.
Once again, many thanks.
Xen