mythbuntu-bugs team mailing list archive

[Alec Leamas <505705@xxxxxxxxxxxxxxxxxx>]

As for the lirc part, the last 0.9.4 release solves this since the lircd
output socket is created at an very early point in the boot sequence.
lircd is started using socket activation when irexec or some otther
client connects to the socket. So, no race is possible.

IMHO, mysql should do the same, and might indeed have so already. Don't
know, closing as fixed.

** Changed in: lirc (Ubuntu)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
https://bugs.launchpad.net/bugs/505705

Title:
  irexec isn't started automatically on existing installs

Status in Mythbuntu:
  Expired
Status in lirc package in Ubuntu:
  Fix Released

Bug description:
  Irexec does not start with the lirc service on 9.10 (Ubuntu+MythTV,
  not Mythbuntu). In my testing, it seems that the following line might
  be the issue.

  (from /etc/init.d/lirc)
  start-stop-daemon --start --quiet --oknodo --exec /usr/bin/irexec -- -d /etc/lirc/lircrc < /dev/null

  I've compared my two systems and there doesn't seem to be that big of
  difference (one is Mythbuntu, the other is Ubuntu+MythTV). The
  Mythbuntu system works correctly where the Ubuntu+MythTV does not.

  /etc/lirc/lircrc does not exist on either system.

  If I edit the line to just

  start-stop-daemon --start --quiet --oknodo --exec /usr/bin/irexec --

  Then it does work, but it stays in the terminal and thus is not really
  a viable option.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mythbuntu/+bug/505705/+subscriptions