<div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">You shouldn't need to run mythfilldatabase from a frontend. It should<br>be run on a backend (as a matter of fact, it should be run /only/ on the
<br>master backend).<br><br>Also, if you're in the US, allowing the master backend to automatically<br>run mythfilldatabase is /very much/ the preferred solution (over cron)<br>because it allows Myth to do so at whatever time TMS asked you to run
<br>again. Therefore, TMS is able to spread out resource usage--which means<br>that DataDirect is less likely to fail, which means that we will be able<br>to continue to get high-quality listings data for MythTV.<br><br>
Mike</blockquote><div><br>I have a single combined BE/FE, and thinking about it the setting is configured from the frontend but run by the backend. Is this correct?<br><br>The cron job I use randomises the time mythfilldatabase is called using a "sleep $(expr $RANDOM \% 14400);", but if it is really the backend that runs the mythfilldatabase command I will use that method seeing it now works. I would prefer to be able to configure the mythfilldatabase job from the settings page as it seems "more proper" :-)
<br><br>Thinking about it, mythbackend has to run the job or the $HOME variable wouldn't have an impact on the job's success as I always run mythfrontend manually after logging in (actually about to fix this up as it is a dedicated box), ie the $HOME variable is properly set. I simply hadn't investigated what the issue was, lazy I guess.
<br><br>PS: Yes, I am an Aussie - but still don't want to hammer our guide source.<br><br>Cameron.<br></div></div>