2010-09-30, 14:46
^^ For the doover process I made a change last night in the SVN for you. --unmanned_doover provides a way to set up an "at" or "cron" job to perform the doover at a regular interval.
It should go something like this:
I think this should allow flexability in the --doover process without requiring mythicalLibrarian to keep track of the state of the jobs which ran previously.
Another option could be to include an option where if it has been 24 hours (according to TheTvDb). I'm still working out the kinks on this because it requires sudo access. I may be able to come up with something more perminant within the week. I'd say 12-24 hours would be an appropriate timeframe to run the --doover que. It can put a large strain on a server.
Also, yes, if 2 update commands are run at the same time then one will start the update process and the seccond will stop it. Take a moment to post in this thread that you are experienceing this issue http://forum.xbmc.org/showthread.php?tid=82133
It should go something like this:
Code:
sudo -u mythtv sudo mythicalLibrarian --unmanned_doover
Another option could be to include an option where if it has been 24 hours (according to TheTvDb). I'm still working out the kinks on this because it requires sudo access. I may be able to come up with something more perminant within the week. I'd say 12-24 hours would be an appropriate timeframe to run the --doover que. It can put a large strain on a server.
Also, yes, if 2 update commands are run at the same time then one will start the update process and the seccond will stop it. Take a moment to post in this thread that you are experienceing this issue http://forum.xbmc.org/showthread.php?tid=82133