On 14/04/17 10:15, Hans-J. Ullrich wrote:
Sadly I have to tell, the latest version of lirc is spamming syslog with
mwessages. To make sure, it is not a problem of an earlier configuration, I
deinstalled it completely and reinstalled it new.
The message, which is spamming is the following:
Apr 11 20:28:22 localhost lircd-0.9.4c[8159]: Error: Cannot glob /sys/class/
rc/rc0/input[0-9]*/event[0-9]*
Apr 11 20:28:23 localhost lircd[8159]: lircd-0.9.4c[8159]: Error: Cannot glob
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
Apr 11 20:28:23 localhost lircd-0.9.4c[8159]: Error: Cannot glob /sys/class/
rc/rc0/input[0-9]*/event[0-9]*
Apr 11 20:28:24 localhost lircd[8159]: lircd-0.9.4c[8159]: Error: Cannot glob
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
and so on.
Note: Although I have no infrared hardware installed, this issue did not happen
with earlier versions.
As a workaround, I had to deinstall the package for now.
It would be nice, if you could take an eye on it.
Hi, thanks for reporting!
I cannot see that lircd does anything wrong here. The basic message is
that your lirc setup isn't properly configured, which is a simple fact
if you don't have any IR hardware. There are many options in this
situation:
- You could uninstall lirc - and if you don't plan to use it it's
certainly a sensible thing to do.
- You could disable lircd.socket and and lircd.service if you plan to
use it later, leaving package in place.
- You could raise the loglevel in /etc/lirc/lirc_options.conf to mute
the message, if you for some reason want to run lircd despite the
message (but why?).
- Last but not least, you could try to configure lirc. In this case, the
above message is indeed helpful in some situations.
So, my basic understanding is that this issue should be closed as
not-a-bug. I will close it unless there is more input.
Cheers!
--alec
