mythbuntu-bugs team mailing list archive

[Joel Ebel <698007@xxxxxxxxxxxxxxxxxx>]

I've tested that this patch applies cleanly to natty.  I have not, and
likely won't be able to, test the functionality with natty, as my two IR
devices are in use in a mythtv machine I'm unwilling to reinstall with
natty.

** Patch added: "patch that merges the patches from both bugs"
   https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/698007/+attachment/1957482/+files/lirc.init.patch

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

Title:
  lirc init script can create circular symlinks

Status in “lirc” package in Ubuntu:
  New

Bug description:
  Binary package hint: lirc

  This is related to bug 697999 and specifically my need to work around
  that bug.

  If, in /etc/lirc/hardware.conf, you set REMOTE_SOCKET to /dev/lircd1
  and transmitter_socket to /dev/lircd, then the lirc init script will
  create a circular symlink loop between /dev/lircd and /dev/lircd1.
  The script tests if OLD_SOCKET != REMOTE_SOCKET, but it should also
  make sure that OLD_SOCKET != TRANSMITTER_SOCKET  Additionally, before
  removing ${OLD_SOCKET}1 the script should do the same checks, which it
  currently does none.

  A patch for this solution is attached.

  My preference would actually to be to use the new socket locations in
  /var/run/lircd, however, then the the order I create those sockets is
  irrelevant, as the magical symlinking always symlinks /dev/lircd to
  the remote and /dev/lircd1 to the transmitter, which is backwards from
  how I need it to be.  I'm not actually sure what the best fix is here.
  Perhaps it could just test if the socket is /var/run/lirc/lircd\d+ and
  if it is, then just symlink to /dev/$(basename $REMOTE_SOCKET)  If
  this is an acceptable solution, I can probably write up a patch for
  this behavior if necessary.  However, there may be other cases the
  current behavior is designed to correct for.  If bug 697999 gets
  fixed, then this problem will no longer affect me.