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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768291

Title:
  lirc is flooding the syslog with two lines each second

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1768291/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to