lirc does not spam the log if correctly configured. The repeated messages is a actually a feature since it's an easy way to detect status when configuring and hot-plugging a device.
The basic issue here is if lirc is pulled in as a dependency. It should not, it's designed to be used by users which actually have the need. The only rdepends I find in Sid is a Recommends in the vdr package. I'll file an issue about that. Once this is fixed, no-one will have lirc installed "by accident" so to speak. For users which does not use lirc there are two options. One is to remove the package completely, this should be possible on all installations since there are no hard rdepends, just a Recommends in the vdr package. The other is to disable lircd.socket and lircd.uinput using systemctl. This is nothing special, it's standard system service configuration. Besides the R: lirc in the vdr package I thus still don't see any actual bug here. What *could* be considered is to add some info to the logged message about disabling services to get rid of it. Allowing a unused service to continue to run as root without spamming the log is wrong for security and performance reasons. Hence, just writing the log message once is IMHO not a viable alternative. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1768291 Title: lirc is flooding the syslog with two lines each second Status in lirc package in Ubuntu: Triaged Bug description: Hello, in the syslog every second two lines are written: May 1 18:05:19 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:19 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:20 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:20 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:21 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:21 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:22 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:22 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:23 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:23 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:24 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:24 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:25 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:25 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:26 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:26 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:27 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:27 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:28 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:28 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* This is not only annoying as it makes it difficult to use the syslog for checking the system, but also it writes too much data into the log (18MB each day). Also it keeps the hard disc awaken what is bad for standby. Kubuntu 18.04 ii liblirc-client0:amd64 0.10.0-2 amd64 infra-red remote control support - client library ii liblirc0:amd64 0.10.0-2 amd64 Infra-red remote control support - Run-time libraries ii lirc 0.10.0-2 amd64 Infra-red remote control support - daemons and utils I do not have infrared remote control hardware. But I cannot purge the packages as other packages I want to keep would be removed as well. Deactivating the services in systemd does not help (or I am doing something wrong?) Greetings Gert To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1768291/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
