[mythtv-users] Remote backend wackyness

[R. G. Newbury]

Josh White wrote:
>> 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.

If you want to ensure that things are running at the end of the boot, 
you can start (restart) them with a line in /etc/rc.d/rc.local  which is 
always run last.

I had a (now forgotten) problem some time ago, and put
'service mythbackend restart' into rc.local. That fixed the timing 
issue. You might try that.

Note that if something like networking REQUIRES that the window manaqer 
(Gnome, KDE) be up and running, this step will not work. On my laptop, 
NetworkManager requires that I enter the password for the key-ring 
before starting up wireless. This of course would be fatal to a 
mythbackend server which needs networking but does not need a GUI.

Geoff



-- 
         Please let me know if anything I say offends you.
          I may wish to offend you again in the future.

          Tux says: "Be regular. Eat cron flakes."