mythbackend restart script
Submitted by Aaron on August 12, 2008 - 1:54pm
Is there a prebuilt script to automatically restart the back end if it dies? My mythbackend process will die from time to time and i would love it would restart automatically so i do not miss any recordings. I am fairly new to linux so i cannot write the script myself. Any pointers?
Make sure you have the
Make sure you have the latest mythdora rpm install 1.5-17 i think..(see the main page if I'm wrong). Then just go into the "mythdora-tools" menu from the frontend and enable the backend check script.
Ryan
Will that work on my setup?
Will that work on my setup? I have 1 backend with 4 tuners(headless box), 1 frontend only and one slave backend with 1 tuner and a frontend. If I enable the backend check script will that enable it on both backend machines? Or is there a way to do it via ssh?
If your headless backend is
If your headless backend is mythdora 5. Just touch /var/mythdora/.becheck and the service should be enabled. However... Make sure it's at the latest mythdora rpm 1.5-17.. there was an error in the initial release.
Ryan
Thanks Ryan, when you say
Thanks Ryan, when you say touch what do I have to do? What would I do to disable it? Does this start a cron job? How often does it check if the process is running? How can I check which rpm I am using? Thanks!
Aaron- touch means
Aaron-
touch means touch....
man touch
man rpm
Not trying to be a dick...but it's better you learn some things in the process :).
It will start a cronjob that runs every minute to see if the backend is running/connected.
Ryan
ok I read about the touch
ok I read about the touch command and it will basically put a blank file called .becheck in that directory. When it does that does that create a cron job? Otherwise when looking in that directory there is no file called .becheck. Sorry for being a newb. I really have learned a lot about linux since using mythdora for over a year now. I am slowly learning.
There should already be a
There should already be a cron job created.
List them using
crontab -l
or edit
crontab -e
You should see an entry that checks for the existence of .becheck, if its not there it doesnt do anything.
Google crontab for some more info on the syntax of the crontab file.