Bug#860551: [Pkg-lirc-maint] Bug#860551: lircd-0.9.4c[845]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*

2017-05-23 Thread Borden Rhodes
On Mon, 15 May 2017 16:50:17 +0200 Michael Kolmodin wrote: > Actually, there is yet another way to cope with this: adding the > immediate-init option to lircd (e. g., in lirc_options.conf). This will > make lircd exit if the hardware cannot be initialized. Which means there >

Bug#860551: [Pkg-lirc-maint] Bug#860551: lircd-0.9.4c[845]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*

2017-05-15 Thread Michael Kolmodin
Actually, there is yet another way to cope with this: adding the immediate-init option to lircd (e. g., in lirc_options.conf). This will make lircd exit if the hardware cannot be initialized. Which means there will be no socket for clients to connect to. Making this the default setup is a

Bug#860551: [Pkg-lirc-maint] Bug#860551: lircd-0.9.4c[845]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*

2017-05-05 Thread Alec Leamas
I have done some more testing. It seems that on a system with lircd.socket started but no clients running this logging does not occur. Which means that the the excessive logging is the result of some client repeatedly trying to access the lircd socket, but is denied since lircd disconnects

Bug#860551: [Pkg-lirc-maint] Bug#860551: lircd-0.9.4c[845]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*

2017-04-18 Thread Alec Leamas
On 18/04/17 15:03, Sebastian Niehaus wrote: Hi! Thanks for reporting! lircd produces high load on loggin: syslog says lircd-0.9.4c[845]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* not sure if I have done something wrong ... The thing is that the default lirc