Hello, if I'm not mistaken, this bug, or rather the current "solution" with restart-or-reload is why I keep seeing lots of messages like this:
Aug 05 16:19:07 argentum systemd[1]: Starting Laptop Mode Tools - Battery Polling Service... Aug 05 16:19:07 argentum systemd[1]: Reloading Laptop Mode Tools. Aug 05 16:19:07 argentum systemd[1]: Started Laptop Mode Tools - Battery Polling Service. Aug 05 16:19:07 argentum laptop_mode[27209]: Laptop mode Aug 05 16:19:07 argentum laptop_mode[27209]: enabled, not active [unchanged] Aug 05 16:19:07 argentum systemd[1]: Reloaded Laptop Mode Tools. Aug 05 16:22:07 argentum systemd[1]: Starting Laptop Mode Tools - Battery Polling Service... Aug 05 16:22:07 argentum systemd[1]: Reloading Laptop Mode Tools. Aug 05 16:22:07 argentum systemd[1]: Started Laptop Mode Tools - Battery Polling Service. Aug 05 16:22:07 argentum laptop_mode[27468]: Laptop mode Aug 05 16:22:07 argentum laptop_mode[27468]: enabled, not active [unchanged] Aug 05 16:22:07 argentum systemd[1]: Reloaded Laptop Mode Tools While I do understand that the current solution is technically sound, it produces many somewhat useless messages in the journal. At first sight such behavior looks like a problem. It also spams the log and makes it harder to read. It could even be argued that it defeats the package's purpose, because it increases the number of writes to logs on disks. Could something be done about this, please? At least this "feature" should respect the CONTROL_BATTERY_LEVEL_POLLING=0 setting. It seems wasteful to run lmt-udev to do essentially nothing in this case. I've submitted this call for change as an issue [1] at the upstream site. Kind regards, Ondrej Grover [1] https://github.com/rickysarraf/laptop-mode-tools/issues/106
