Tvheadend

Try /bin/sh /usr/local/bin/post-record >> /home/xbmc/wakeup.log (or whatever shell scripting language you're using, obviously) - especially if you haven't declared the shell type at the start of your script (i.e. #!/bin/sh or similar as your first line)

Thanks for the reply.

post-record is a ruby script, with #!/bin/env ruby as the shebang.
I've tried prefixing the command with both ruby and /usr/bin/ruby (both of these work as expected from the shell) but to no avail.

What shell are you launching the script from when you're at the command line? Try that - spawn a bash and let that call ruby (for example).

I'm using bash. I've tried /bin/bash /usr/local/bin/post-record >> /home/xbmc/wakeup.log and /bin/bash -c "/usr/local/bin/post-record >> /home/xbmc/wakeup.log" but as the post-processor command but still no joy.

More random thoughts, then...!

Related to the redirection, perhaps? Does it work without the redirect, or if you do something like >> wakeup.log 2>&1?

Is the script accessible and executable to the UID that's running tvheadend (e.g. hts:video)?

It didn't work without the redirect, I added it to see if I could work out whether it was running or not. 2>&1 doesn't seem to help.

The script's mode is 755, the log file is 777, and I've verified that logging in as hts:video allows me to execute the script.

Hmmm. Can you share the script? I have to suspect it's something in there, then, because everything else looks okay... happy to give it a whirl on my rig if you like.

Sure, I've stuck it in a GitHub Gist here: https://gist.github.com/marxjohnson/11356234
Thanks!

Without running it, I'd still point an accusing finger at your shebang definition. You've got #!/usr/bin/env ruby - is this valid for the hts user, though? Is ruby in the PATH when this script is spawned even if it's in your path when you open a shell to test it?

Three thoughts:

1. Try a new script that dumps env to a file; call that as a test; see what PATH is defined and whether ruby is thus valid
2. Explicitly define the PATH when calling the existing script
3. Explicitly define the path to ruby instead of relying on /usr/bin/env

Success!
I tried various things inspired by your comments.

First I created the following bash script and set it to run as the post-processor command:

#!/bin/bash
/usr/bin/env > /home/hts/out

#!/bin/bash
/usr/bin/ruby /usr/local/bin/post-record.rb >> /home/xbmc/wakeup.log 2>&1

So, I installed rvm and installed a newer version of ruby, then changed the bash script to

#!/bin/bash
source /etc/profile.d/rvm.sh
rvm use 2.0
ruby /usr/local/bin/post-record.rb >> /home/xbmc/wakeup.log 2>&1

Thanks very much for your help