Menu
▾
▴
lirc-list
|
From: James A R B. <jam...@gm...> - 2015-04-13 08:09:51
|
Hi, I have tried building lirc 0.9.2+ on top of Ubuntu 14.04, as Ubuntu not shipping with anything newer than 0.9.0. Not even a working PPA. I can get lirc all running ok, works fine in Mythtv, but I am having trouble with irexec and other lirc apps not finding the lircd socket. The lircd process is up as root@tvlounge:~# ps ax |grep lirc 25414 pts/5 S+ 0:00 grep --color=auto lirc 32145 ? Ss 0:00 /usr/sbin/lircd --output=/var/run/lirc/lircd --driver=default --device=/dev/lirc0 root@tvlounge:~# lircd -v lircd 0.9.2a root@tvlounge:~# uname -p x86_64 But, irexec gives root@tvlounge:~# irexec /etc/lirc/lircrc do_connect: could not connect to socket connect: No such file or directory irw connect: No such file or directory But push the socket and it works root@tvlounge:~# irw /var/run/lirc/lircd 0000000000000002 00 KEY_UP beo5 0000000000000002 01 KEY_UP beo5 0000000000000002 02 KEY_UP beo5 Have even tried pushing the environment variable mentioned in man irexec root@tvlounge:~# LIRC_SOCKET_PATH=/var/run/lirc/lircd root@tvlounge:~# echo $LIRC_SOCKET_PATH /var/run/lirc/lircd root@tvlounge:~# irexec /etc/lirc/lircrc do_connect: could not connect to socket connect: No such file or directory Any help and pointers much appreciated, even ./configure options for the build. James |
|
From: Alec L. <lea...@gm...> - 2015-04-13 08:39:37
|
On 13/04/15 10:09, James A R Brown wrote: > Hi, > > I have tried building lirc 0.9.2+ on top of Ubuntu 14.04, as Ubuntu not > shipping with anything newer than 0.9.0. Not even a working PPA. > > I can get lirc all running ok, works fine in Mythtv, but I am having > trouble with irexec and other lirc apps not finding the lircd socket. > > The lircd process is up as > > root@tvlounge:~# ps ax |grep lirc > > 25414 pts/5 S+ 0:00 grep --color=auto lirc > > 32145 ? Ss 0:00 /usr/sbin/lircd --output=/var/run/lirc/lircd --driver=default --device=/dev/lirc0 > > root@tvlounge:~# lircd -v > > lircd 0.9.2a > > root@tvlounge:~# uname -p > > x86_64 > > > But, irexec gives > > root@tvlounge:~# irexec /etc/lirc/lircrc > > do_connect: could not connect to socket > > connect: No such file or directory > > > irw > > connect: No such file or directory > > > But push the socket and it works > > root@tvlounge:~# irw /var/run/lirc/lircd > > 0000000000000002 00 KEY_UP beo5 > > 0000000000000002 01 KEY_UP beo5 > > 0000000000000002 02 KEY_UP beo5 > > > Have even tried pushing the environment variable mentioned in man irexec > > root@tvlounge:~# LIRC_SOCKET_PATH=/var/run/lirc/lircd > > root@tvlounge:~# echo $LIRC_SOCKET_PATH > > /var/run/lirc/lircd > > root@tvlounge:~# irexec /etc/lirc/lircrc > > do_connect: could not connect to socket > > connect: No such file or directory > Here are many things to check: - Is the socket available and accessible (ls -l /var/run/lirc/lircd)? - Have you exported the shell variable (export LIRC_SOCKET_PATH)? - Is there any useful info in the logs (syslog as long as you don't use a log file argument)? - Is there anything in the logs after raising the log level (e. g., using --loglevel=debug to lircd?) Cheers! --alec |
|
From: James A R B. <jam...@gm...> - 2015-04-13 10:07:22
|
On 13/04/15 09:39, Alec Leamas wrote: > On 13/04/15 10:09, James A R Brown wrote: >> Hi, >> >> I have tried building lirc 0.9.2+ on top of Ubuntu 14.04, as Ubuntu not >> shipping with anything newer than 0.9.0. Not even a working PPA. >> >> I can get lirc all running ok, works fine in Mythtv, but I am having >> trouble with irexec and other lirc apps not finding the lircd socket. >> >> The lircd process is up as >> >> root@tvlounge:~# ps ax |grep lirc >> >> 25414 pts/5 S+ 0:00 grep --color=auto lirc >> >> 32145 ? Ss 0:00 /usr/sbin/lircd >> --output=/var/run/lirc/lircd --driver=default --device=/dev/lirc0 >> >> root@tvlounge:~# lircd -v >> >> lircd 0.9.2a >> >> root@tvlounge:~# uname -p >> >> x86_64 >> >> >> But, irexec gives >> >> root@tvlounge:~# irexec /etc/lirc/lircrc >> >> do_connect: could not connect to socket >> >> connect: No such file or directory >> >> >> irw >> >> connect: No such file or directory >> >> >> But push the socket and it works >> >> root@tvlounge:~# irw /var/run/lirc/lircd >> >> 0000000000000002 00 KEY_UP beo5 >> >> 0000000000000002 01 KEY_UP beo5 >> >> 0000000000000002 02 KEY_UP beo5 >> >> >> Have even tried pushing the environment variable mentioned in man irexec >> >> root@tvlounge:~# LIRC_SOCKET_PATH=/var/run/lirc/lircd >> >> root@tvlounge:~# echo $LIRC_SOCKET_PATH >> >> /var/run/lirc/lircd >> >> root@tvlounge:~# irexec /etc/lirc/lircrc >> >> do_connect: could not connect to socket >> >> connect: No such file or directory >> > > Here are many things to check: > > - Is the socket available and accessible (ls -l /var/run/lirc/lircd)? > - Have you exported the shell variable (export LIRC_SOCKET_PATH)? > - Is there any useful info in the logs (syslog as long as you don't > use a log file argument)? > - Is there anything in the logs after raising the log level (e. g., > using --loglevel=debug to lircd?) > > > Cheers! > > --alec > > Hi Alec, 1) Yes root@tvlounge:~# ls -l /var/run/lirc/lircd srw-rw-rw- 1 root root 0 Apr 13 09:04 /var/run/lirc/lircd 2) *Doh* Exported and irexec now works 3) Nothing exceptional..... tried also to start irw and irexec, but nothing appended to log root@tvlounge:~# lircd --loglevel=debug --driver=default --device=/dev/lirc0 -n /etc/lirc/lircd.conf lircd-0.9.2a[24777]: Warning: Running as root lircd-0.9.2a[24777]: Info: Using remote: beo5. lircd-0.9.2a[24777]: Info: Using remote: kinivq. lircd-0.9.2a[24777]: Info: Using remote: rmt-b128p. lircd-0.9.2a[24777]: Info: Using remote: rmt-b128p-tv. lircd-0.9.2a[24777]: Info: Using remote: SONY_RMT_B104P. lircd-0.9.2a[24777]: Info: Using remote: SONY. lircd-0.9.2a[24777]: Warning: SONY: garbage after 'name' token in line 76 ignored lircd-0.9.2a[24777]: Notice: lircd(default) ready, using /var/run/lirc/lircd lircd-0.9.2a[24777]: Notice: accepted new client on /var/run/lirc/lircd So still wondering why irw and irexec can not find the right path.... is there a configure option? I have just re-run, ./configure (no options), make clean, make, make install and still irw and irexec do not find the socket without being pushed in the right direction. James |
|
From: Alec L. <lea...@gm...> - 2015-04-13 12:39:41
|
On 13/04/15 12:09, James A R Brown wrote: > Hummm.... /usr/local/var/run/lirc/lircd is default created path for my > configure? These are the autotools defaults. There are many ways to change this, one is to use --prefix=... to configure, another to use the runtime --output option on command line or in lirc_options.conf Packaged versions normally sets prefix to /usr -> default socket becomes /var/run/lirc/lircd Cheers! --alec PS: Please don't top-post. DS |
|
From: Alec L. <lea...@gm...> - 2015-04-13 19:48:59
|
On 13/04/15 21:25, James A R Brown wrote: > > On 13/04/15 13:38, Alec Leamas wrote: >> On 13/04/15 12:09, James A R Brown wrote: >>> Hummm.... /usr/local/var/run/lirc/lircd is default created path for my >>> configure? >> >> These are the autotools defaults. The >re are many ways to change this, >> one is to use --prefix=... to configure, another to use the runtime >> --output option on command line or in lirc_options.conf >> >> Packaged versions normally sets prefix to /usr -> default socket >> becomes /var/run/lirc/lircd >> >> >> Cheers! >> >> --alec >> >> PS: Please don't top-post. DS >> > > Hi Alec, > > To clarify your mail > > If i set the prefix to /usr the socket then created is at > /usr/var/run/lirc/lircd not /var/run/lirc/lircd as your mail says. > > So I guess the prefix should be "" to get /var/run/lirc/lircd socket > which is the default place irw, irsend etc look too? No > So that said, should a default build with no configure options, not put > the lircd socket exactly where the lirc apps expect? > > And only not do that, when a --prefix= option on the configure is used? This is basically not directly related to lirc, it's more about how autotools works. You might want to have a second look at the configure --help output and/or look into the autoconf/automake documentation. That said, it's generally a little tricky to have a non-standard installation. If you just want to test, CONTRIBUTE.md in the source top directory has info on how to run lircd and other tools directly from the build directory without installing. Cheers! --alec PS: Again: Please don't top-post. DS |
|
From: James A R B. <jam...@gm...> - 2015-04-13 19:57:57
|
On 13/04/15 13:38, Alec Leamas wrote: > On 13/04/15 12:09, James A R Brown wrote: >> Hummm.... /usr/local/var/run/lirc/lircd is default created path for my >> configure? > > These are the autotools defaults. There are many ways to change this, > one is to use --prefix=... to configure, another to use the runtime > --output option on command line or in lirc_options.conf > > Packaged versions normally sets prefix to /usr -> default socket > becomes /var/run/lirc/lircd > > > Cheers! > > --alec > > PS: Please don't top-post. DS > Hi Alec, To clarify your mail If i set the prefix to /usr the socket then created is at /usr/var/run/lirc/lircd not /var/run/lirc/lircd as your mail says. So I guess the prefix should be "" to get /var/run/lirc/lircd socket which is the default place irw, irsend etc look too? So that said, should a default build with no configure options, not put the lircd socket exactly where the lirc apps expect? And only not do that, when a --prefix= option on the configure is used? James |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X