[mythtv-users] irexec fails to start on boot

[Alec Leamas]

On 13/01/16 03:36, Robert Dege wrote:
> I'm running mythbuntu 14.04.3 LTS (64bit).  LIRC is running with no
> issues, but I'm unable to get irexec to run:
>
> # lircd -v && irexec -v
> lircd 0.9.0
> irexec 0.9.0
>
>
> # sudo irexec /etc/lirc/lircrc
> irexec: could not connect to socket
> irexec: No such file or directory
>
>
> The lircrc config file points to $USER/.lirc/mythtv
> # ls -l /etc/lirc/lircrc
> lrwxrwxrwx 1 root root 24 Jan 12 20:19 /etc/lirc/lircrc ->
> /home/rob/.lirc/mythtv
>
>
> The only oddity that I notice is that there's two session of lirc
> running, with two pid files:
> # ps -aef | grep lirc
> root      3356     1  0 21:29 ?        00:00:02 /usr/sbin/lircd
> --output=/dev/lircd --driver=devinput
> --device=phys=usb-0000:00:04.0-1/input1 --listen
> --pidfile=/run/lirc/lircd1.pid
> root      3358     1  0 21:29 ?        00:00:00 /usr/sbin/lircd
> --output=/dev/lircd --driver=devinput
> --device=phys=usb-0000:00:04.0-3/input0 --connect=localhost 8765

Hi!

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.

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.

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.

Cheers!

--alec