Specify (in a cross-platform way) where to log service output

[andrewdavidmackenzie]

I am trying to understand my service's failures on macos, but there are no logs (that I can find).

This SO article suggests that specific keys are required in the plist on macos to get stdout and stderr into files I can tail?
(I'm surprised there is no output logged by default - but could be I guess...).

Is there a way to do this, so I can see service output (stdout and/or stderr) on macos, but without having to "break-out" each platform in my code (e.g. use SystemdService etc), as service-manager being cross platform is one of it's greatest advantages for me.

[andrewdavidmackenzie]

An alternative take on this (I find myself back here a year later debugging linux no-service-restart after reboot issues, and find my own issue again :-) ) would be that when ServiceManager.install() is called, there is some way to then get the (OS and service manager dependent) way to get the system chosen location for logging output, and my app can print that path on standard output - and the user can tail it when needed.