Open ajbeamon opened 6 years ago
So, when I fdbmonitor with the --daemonize
flag on macOS, I get the following error:
Kernel extension failed validity check (-67062): /usr/local/libexec/fdbmonitor
So.
But on the flip side, it shows up in the console logs in the place you'd expect!
We should either fix daemonize or have the package start FDB Monitor with the output going somewhere.
On Linux, we run fdbmonitor with the --daemonize flag, which causes it to log to syslog. On macOS, we do not use the --daemonize flag (and I'm not immediately sure why), which results in output going to stderr. As far as I can tell, it doesn't seem that we are capturing stderr anywhere, so this logging output is being lost.