The udev rule lirc 0.7.2 installs makes udev create a /dev/lirc/0 node but the /etc/conf.d/lircd config file it installs says to use /dev/lirc0 by default. Reproducible: Always Steps to Reproduce:
bingo, this *MUST* to be corrected. Since kernel 2.6.13 was released I had to use 0.7.2 so my lirc_gpio module would compile. The affect of this bug is as follows, lirc starts, syslog see's this Sep 18 15:47:07 synapse lircd-0.7.2[8322]: accepted new client on /dev/lircd Sep 18 15:47:07 synapse lircd-0.7.2[8322]: could not open /dev/lirc Sep 18 15:47:07 synapse lircd-0.7.2[8322]: default_init(): Is a directory Sep 18 15:47:07 synapse lircd-0.7.2[8322]: caught signal Sep 18 15:48:59 synapse lircd-0.7.2[8362]: lircd(leadtek_0010) ready So far so good, but the minute you try do something like run irw, lircd dies, syslog gets this Sep 18 15:47:07 synapse lircd-0.7.2[8322]: accepted new client on /dev/lircd Sep 18 15:47:07 synapse lircd-0.7.2[8322]: could not open /dev/lirc Sep 18 15:47:07 synapse lircd-0.7.2[8322]: default_init(): Is a directory Sep 18 15:47:07 synapse lircd-0.7.2[8322]: caught signal After playing around i figured out that starting lircd manually with the -d option as follows lircd -d /dev/lirc/0 works so I came to post a bug. But of course now I've discovered that the you set this option in /etc/conf.d/lircd so setting the correct location fixes. But it's broken by default and is an easy fix!
Created attachment 70859 [details, diff] files/lircd.conf.patch change the default lirc device from /dev/lirc0 to /dev/lirc/0
I had to elaborate today to find out the same thing. Please, fix this one.
thx, fixed in 0.8.0
