Normal
Aha. That explains why so many people (including me) see it working when they press the manual import button, and when the service restarts, but not when their grabber generates the tvguide.xml file to the directory as specified in several guides. How can I add this extra deployment step to my grabber process? I am currently using a task scheduler task to trigger the console version of xmltv gui. I guess I could change the task to run a batch file, but it all seems quite clumsy. My preference, though, would be for the XMLTV import plugin to wait (and keep retrying) until it could get an exclusive write lock on the entire file. This would ensure that the grabbers had finished before the plugin starts to read in the file. Is the source available / can I try to add that to it myself?
Aha. That explains why so many people (including me) see it working when they press the manual import button, and when the service restarts, but not when their grabber generates the tvguide.xml file to the directory as specified in several guides.
How can I add this extra deployment step to my grabber process? I am currently using a task scheduler task to trigger the console version of xmltv gui. I guess I could change the task to run a batch file, but it all seems quite clumsy.
My preference, though, would be for the XMLTV import plugin to wait (and keep retrying) until it could get an exclusive write lock on the entire file. This would ensure that the grabbers had finished before the plugin starts to read in the file. Is the source available / can I try to add that to it myself?
