#7 yes, on a single machine it is sufficient to listen on lo, however it is also sufficient to listen on the regular nic interface. On multiple machine installs it is never OK to just listen on lo (for obvious reasons). For this reason we've decided to make the setting "anything but lo" rather than "lo" as the only time this wouldn't be valid is on machines without any nic (which is far less common)
Fit some reason on your systems, it isn't sending the signal saying something other than lo has started (that is my guys anyway). I'd be interested what happens in the following cases 1) you manually send the signal 2) you attempt a 'sudo service mythtv-backend start' after the system is booted Also, can someone upload their /var/log/upstart/mythtv-backend.log file after it has failed to start at boot. -- You received this bug notification because you are a member of UBUNTU - AL - BR, which is subscribed to Mythbuntu. https://bugs.launchpad.net/bugs/907301 Title: mythtv backend wouldn't start automatically after the latest update Status in Mythbuntu, Ubuntu derivative focused upon MythTV: New Bug description: Mythtv Backend doesn't start on machine boot. The mythtv-backend.conf in /etc/init doesn't trigger, at least on my setup. I think the "start on" conditions are not being met. Latest version: 2:0.24.1+fixes.20111207.40f3bae-0ubuntu0mythbuntu1 Attached is a version that works on my server, with changed "start on" conditions To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/907301/+subscriptions -- Mailing list: https://launchpad.net/~linux-traipu Post to : [email protected] Unsubscribe : https://launchpad.net/~linux-traipu More help : https://help.launchpad.net/ListHelp
