Okay, so I have a couple of convenient scripts that I use for various things on my system, including rsyncing certain files onto a USB stick for taking with me.
I set these up using launchd, and used them for ages under Lion. I didn't bother with any fancy logging and just provided useful messages onto stdout and stderr that I could then look up in Console by searching for the name of my launchd job.
However, in Mountain Lion launchd doesn't seem to send job output to the Console anymore, meaning I either have to adapt my scripts to use their own log-files which would only add complexity to them, or if something doesn't appear to be working I have to run the script manually in Terminal to get the output directly.
Has something changed with launchd to prevent script output from being logged? If so, is there a way that I can re-enable it, some new .plist option or whatever?
I set these up using launchd, and used them for ages under Lion. I didn't bother with any fancy logging and just provided useful messages onto stdout and stderr that I could then look up in Console by searching for the name of my launchd job.
However, in Mountain Lion launchd doesn't seem to send job output to the Console anymore, meaning I either have to adapt my scripts to use their own log-files which would only add complexity to them, or if something doesn't appear to be working I have to run the script manually in Terminal to get the output directly.
Has something changed with launchd to prevent script output from being logged? If so, is there a way that I can re-enable it, some new .plist option or whatever?