Great thanks for that - should be able to let you know that it's worked in about 11 hours when it does its next fill.

OK, well mythfilldatabase did its run and completed OK, but returned the following message:
Last mythfilldatabase run started on 2006-02-08 00:14 and ended on 2006-02-08 00:17. mythfilldatabase ran, but did not insert any new data into the Guide. This can indicate a potential grabber failure.
There's guide data until 2006-02-14 00:10 (6 days).
I got the same result when I ran it manually. I'll run it again a few times manually tomorrow, to see if this is consistent...

Try running the bare command as the mythtv user. If that doesn't tell you anyhting obvious add " -v all" to the command line to enable debugging and redirect stdout and stderr to a log file with something like " >mylogfile 2>&1".

As far as I can tell, it's running OK. Possibly the reason it does not insert any new data into the Guide is because there's no new data to insert, so I'm going to refrain from running it manually for a couple of days and just give it a chance to see how it goes each night with it's automatic run.

Last night's auto fill completed AOK. I've now rebooted to ensure that that doesn't affect anything, and will see how it goes tonight in about 14 hours time.

If you need to pass multiple arguments to the grabber script you need to put in quotes to group them together for mythfilldatabase (so it doesn't think the 2nd argument after --graboptions is for mythfilldatabase's use).

You need to use double backslashes before the quotes 'cos otherwise the script swallows the quotes.

So, the code becomes



<<BOOM-chakka-BOOM-chakka>>
If yo gonna use bash,
Dude use da slash slash!
Wid no slashin' in what's wrote,
Script's gonna swallow up da quote.
Start learnin' dis good,
Big respect in da hood!

Hope that's useful... (apart from the cr@p rap!)

Indulis

Thank you, Indulis, for that injection of...culture. I had no idea Linux had become so hip lately!

Anyway I'm 99% certain this has got it licked - the EPG listings server was n/a last night when Knopp did its auto fill, so an XMLTV error 256 was returned. (I'd still like to find a glossary of those errors somewhere, I couldn't find one on xmltv.org, but I guess it could be buried in compressed documentation somewhere there...)

Also, it would still be useful to know just why I have to set the environment when presumably most others don't have this issue...

Most likely just your grabber choosing a bad place to cache settings, or a bad way to get the path to them. Frankly this is very common problem to encounter when running scripts from cron, or remotely with ssh, or ... I know enough to test stuff like that using "env -i" and still get burned occasionally when I get sloppy.

OK so it's not just me, well that's kind of a relief! Well I think we can put this one to bed now, so thanks very much tjc, paulh & indulus, for all your assistance