> I think its bad practice to log this way on a production system, maybe just
> my opinion.
> Can this be restricted to when a debug option is enabled?
We decided to make logging always-on in repowerd based on bad debugging
experiences with the old USC/powerd combination. This decision has paid
off since it has made it much easier to debug problems in the wild,
especially ones that are hard to reproduce. No need to tell the user to
enable debugging and then try to reproduce it again... when something
goes wrong they can just send us the log file and we will have the full
picture of what was going on in repowerd.
As discussed above, the cost of logging is negligible, so, in my
opinion, we have much to lose and little to gain by disabling full
logging by default. Of course, we can revisit this decision if we find
that the cost-benefit scale is starting to tip the other way.
Also note that repowerd logs are log-rotated, so there is no risk of
taking up too much disk space.
> Otherwise I am in favor of not spamming syslog.
Sure, I will remove /v/l/syslog output.
** Changed in: repowerd (Ubuntu)
Assignee: (unassigned) => Alexandros Frantzis (afrantzis)
** Changed in: repowerd (Ubuntu)
Importance: Undecided => Low
** Changed in: repowerd (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674736
Title:
messages are logged on every input event
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/repowerd/+bug/1674736/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
