Is there a required/expected environment?

[smaddock]

When I run a script manually, flog logs messages correctly. When I run the script via a LaunchDaemon, flog logs the level, subsystem and category but the message is blank. I know the launchd environment outside of a console session is quite minimal... is there some env variable flog is expecting to be set? Some other parameter in my LaunchDaemon I need to set for flog to function?

[smaddock]

I think this is the relevant bit:

Error   taskgated: (libsqlite3.dylib) [com.apple.libsqlite3:logging-persist] cannot open file at line 49441 of [1b37c146ee]
Error   taskgated: (libsqlite3.dylib) [com.apple.libsqlite3:logging-persist] os_unix.c:49441: (2) open(/private/var/db/DetachedSignatures) - No such file or directory
Default taskgated: (Security) [com.apple.securityd:security_exception] MacOS error: -67062
Info    kernel: (Quarantine) responsibility for flog[11468] set to that of flog[11468]: /usr/local/Cellar/flog/1.6.4/bin/flog
Info    flog: [com.gocirrus.autopkg_conductor:conductor] 
Info    diagnosticd: [com.apple.diagnosticd:] New connection from peer 11468

[smaddock]

I tried ad-hoc code-signing flog which got rid of the errors but did not change the behavior, and still getting the kernel quarantine message. There's no quarantine flag on the binary. I need to get our updated Developer ID Application cert from my boss to try signing it with a trusted certificate. I wonder if it also needs a PPPC permission granted.

[marcransome]

Can you confirm whether release v1.7.0 is affected? I suspect the requirement for stdin to be connected to a terminal in previous versions may be responsible for this.

[smaddock]

v1.7.0 resolves this issue as well! 🎉 Thank you!

[marcransome]

FYI Release v1.7.2 will be made available shortly with further improvements to the message parsing logic, improved test coverage, and additional man page documentation.