Joined
·
5,241 Posts
sounds like the thread for this question:
I'm using zap2xml and a no internal grabber setting for my epg, importing my own xmltv.xml file to update my epg. Works fine, but where is the setting to remove the old epg info, say for the days already past? I'm looking to to get 14 days of guide populated, but seems like
it keeps the old guide info in the mythconverg mysql database, so I can't seem to get past Jan 1st. (Dec 18 thru Jan 1st is populated).
once i get this working the way i want, only thing left to do is cron it up..
here is my script:
edit: I think I found how to get past jan 1st, had a typo here..
from:
/usr/bin/mythfilldatabase --update --file -l xmltv.xml
to:
/usr/bin/mythfilldatabase --update --file 1 xmltv.xml
This gets me past January 1st now, but still doesn't delete the old epg info.
Must be a reason we're keeping it around? For recordings maybe?
I'm using zap2xml and a no internal grabber setting for my epg, importing my own xmltv.xml file to update my epg. Works fine, but where is the setting to remove the old epg info, say for the days already past? I'm looking to to get 14 days of guide populated, but seems like
it keeps the old guide info in the mythconverg mysql database, so I can't seem to get past Jan 1st. (Dec 18 thru Jan 1st is populated).
once i get this working the way i want, only thing left to do is cron it up..
here is my script:
Code:
#!/bin/sh
# remove old cache files
rm /path/to/zap2xml/cache/*.gz
# path where zap2xml.pl is
cd /path/to/zap2xml
# grab 14 days worth from zap2it account
/usr/bin/perl zap2xml.pl -u username -p password -d 14
# import new xmltv.xml file to mythconverg database
/usr/bin/mythfilldatabase --update --file 1 xmltv.xml
from:
/usr/bin/mythfilldatabase --update --file -l xmltv.xml
to:
/usr/bin/mythfilldatabase --update --file 1 xmltv.xml
This gets me past January 1st now, but still doesn't delete the old epg info.
Must be a reason we're keeping it around? For recordings maybe?