As of late, it ceased to run properly. Turns out some messages to log contain fancy characters like real apostrophes,
’. To fix this, add the following statement to the launchd configuration script:
<key>EnvironmentVariables</key> <dict> <key>LANG</key> <string>en_US.UTF-8</string> </dict>
This will enable UTF-8 character encoding. In plain English, this means the script will be able to recognize such fancy characters where it previously choked and died.
For brevity, update your scripts in accordance to my Gist on GitHub, or have a look at the code below:
Cheers to Brett for the initial version!