[mythtv-users] Remote backend wackyness

[Josh White]

>
> I'm pretty confident in my tuner configuration; I've checked that many
> times, and whenever I do make a change, I delete and re-do all of it.
>
> In general, what I gather from what you say is that my problem could likely
> have to do with the order the backend process and the networking processes
> start.  If the machine tries to load the backend before there's a network
> connection, the backend process will stop itself because it cannot
> communicate.  I believe I've seen this occur, and I was able to make it work
> (accidentally) by running mythfilldatabase after exiting mythbackend-setup
> (which stops/starts the backend process in the process).  Since the machine
> was completely up and running, the network was present, and when the backend
> process was restarted...ah ha!
>
> So to me, it would seem logical to make sure the order in which these
> processes start are what they should be.  This is something I'm not very
> familiar with...the closest thing I've configured like this would probably
> be the autoexec.bat file on my old 486sx running DOS 6.2.  Is there an
> analogous file(s) that I could simply reorder to guarantee that things load
> in the proper order?  One would think that the Mythbuntu people would handle
> that, but I'm clearly unaware of all that goes into this.  If that's not
> possible, then would it be possible to write a simple script to verify
> mythbackend is running at the end of the boot cycle, starting it if not?
>
> My hardware and software configuration isn't that exotic, it seems strange
> that such a basic issue could be causing my trouble.
>


So after actually taking the time to read the link, it sounds like the
problem/solution is something like I surmised. Sounds like I'll be spending
some time learning how to tweak my boot sequence.

Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mythtv.org/pipermail/mythtv-users/attachments/20090522/0edcd00d/attachment.htm>