mythbuntu-bugs team mailing list archive

[Mario Limonciello <superm1@xxxxxxxxxx>]

The intention for the rule is to start when an interface that isn't lo
comes up (be it eth0, wlan0, what not).  It sounds like at least for your
scenario that doesn't work properly.

We don't want to trigger on lo itself.

On Tue, Dec 27, 2011 at 15:11, limcearna <907301@xxxxxxxxxxxxxxxxxx> wrote:

> The rule defined in the current file in the distribution is IFACE!=lo.
> I'm new to upstart but that would indicate to me that we're expecting lo
> not to be up.
>
> It is as per the Upstart doc (http://upstart.ubuntu.com/cookbook/#id175)
> but not as per the "Startup Process"
> (http://upstart.ubuntu.com/cookbook/#id123)
>
> If I set it to IFACE!=lo it won't start.
> It starts when I  set it to IFACE=lo and started udev-finish
>
> Should this be the configuration?
>
> --
> You received this bug notification because you are a member of Mythbuntu
> Bug Team, 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/~mythbuntu-bugs
> Post to     : mythbuntu-bugs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~mythbuntu-bugs
> More help   : https://help.launchpad.net/ListHelp
>



-- 
Mario Limonciello
superm1@xxxxxxxxx