<div dir="ltr"><div><div><div>Alec,<br><br></div>The socket location was the problem. In /etc/lirc/hardware.conf, I set REMOTE_SOCKET="/dev/lircd". Even though /dev/lircd was a soft link to /var/run/lirc/lircd, irexec was failing since it wasn't following the sym link. I updated the REMOTE_SOCKET variable to point to /var/run/lirc/lircd, and now it works fine.<br><br></div>Thanks!<br><br></div>-Robert<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 13, 2016 at 2:29 PM, Alec Leamas <span dir="ltr"><<a href="mailto:leamas.alec@gmail.com" target="_blank">leamas.alec@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 13/01/16 03:36, Robert Dege wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'm running mythbuntu 14.04.3 LTS (64bit). LIRC is running with no<br>
issues, but I'm unable to get irexec to run:<br>
<br>
# lircd -v && irexec -v<br>
lircd 0.9.0<br>
irexec 0.9.0<br>
<br>
<br>
# sudo irexec /etc/lirc/lircrc<br>
irexec: could not connect to socket<br>
irexec: No such file or directory<br>
<br>
<br>
The lircrc config file points to $USER/.lirc/mythtv<br>
# ls -l /etc/lirc/lircrc<br>
lrwxrwxrwx 1 root root 24 Jan 12 20:19 /etc/lirc/lircrc -><br>
/home/rob/.lirc/mythtv<br>
<br>
<br>
The only oddity that I notice is that there's two session of lirc<br>
running, with two pid files:<br>
# ps -aef | grep lirc<br>
root 3356 1 0 21:29 ? 00:00:02 /usr/sbin/lircd<br>
--output=/dev/lircd --driver=devinput<br>
--device=phys=usb-0000:00:04.0-1/input1 --listen<br>
--pidfile=/run/lirc/lircd1.pid<br>
root 3358 1 0 21:29 ? 00:00:00 /usr/sbin/lircd<br>
--output=/dev/lircd --driver=devinput<br>
--device=phys=usb-0000:00:04.0-3/input0 --connect=localhost 8765<br>
</blockquote>
<br></span>
Hi!<br>
<br>
The culproit is probably simple: irexec doesn't know that you are using /dev/lirc as the lircd output socket. You need to tell it, but I'm unsure if it's possible in 0.9.0, in modern lirc it works, though.<br>
<br>
So, your setup could be improved. Using /dev/lirc is basically a bad idea, it's udev's task to create entrys in /dev. Better then to stick to the (modern) default /run/lirc/lircd. Using the default socket also means thatirexec will find it.<br>
<br>
Also, usiing the same output socket in two lircd processes is basically a no-go. You get away with it since the connecting instance forwards events to the other instance over TCP instead of sending them to the socket. Still, I think it would be clearer if you gave each instance a unique output socket.<br>
<br>
Cheers!<br>
<br>
--alec<br>
<br>
_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org" target="_blank">mythtv-users@mythtv.org</a><br>
<a href="http://lists.mythtv.org/mailman/listinfo/mythtv-users" rel="noreferrer" target="_blank">http://lists.mythtv.org/mailman/listinfo/mythtv-users</a><br>
<a href="http://wiki.mythtv.org/Mailing_List_etiquette" rel="noreferrer" target="_blank">http://wiki.mythtv.org/Mailing_List_etiquette</a><br>
MythTV Forums: <a href="https://forum.mythtv.org" rel="noreferrer" target="_blank">https://forum.mythtv.org</a><br>
</blockquote></div><br></div>