<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">on my production system which is on 16.04, anytime I need to did maintenance, I’d just reboot and I’d know that it would come up clean and mythtv-backend would be running.<div class=""><br class=""></div><div class="">Right now, if I reboot that system, I have to do ‘sudo systemctl start mythtv-backend’ to get the backend running again.</div><div class=""><br class=""></div><div class="">I’ve been doing some testing on a new test mythtv system and I modified XMLTV by changing the Zipcode that the json grabber was pulling data from. I started this a few days ago and noticed today that the production system has not update the schedules due to an grabber error.</div><div class=""><br class=""></div><div class="">So I reconfigured the XMLTV stuff on the production system and updated the database. In doing this I do sudo systemctl stop mythtv-backend before I run mythtv-setup and edited the channels. Since then I’ve had to ‘sudo systemctl start mythtv-backend’ after rebooting</div><div class=""><br class=""></div><div class="">Is this fixable??</div><div class=""><br class=""></div><div class="">I’d like mythtv-backend to start on boot.</div><div class=""><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Jim Abernathy<br class=""><a href="mailto:jfabernathy@gmail.com" class="">jfabernathy@gmail.com</a><br class=""><br class=""><br class=""></div>
</div>
<br class=""></div></body></html>