Log output far too verbose
Bug #31512 reported by
Daniel Silverstone
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
acpid (Debian) |
Fix Released
|
Unknown
|
|||
acpid (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Currently the acpid log output is far too verbose.
Ideally it would be small enough that we could log it using syslog to daemon.log but since it currently produces ca. 17 lines of log for each battery event in my laptop, said events occurring semi-regularly and producing around 60 to 90 thousand lines of log per day, it would be too much to syslog right now.
There are various ways to make it simpler (E.g. not sending the handler-output log lines if there's no handler output) and we should look into these
Changed in acpid: | |
status: | Unknown → New |
Changed in acpid: | |
status: | New → Fix Released |
To post a comment you must log in.
This is causing bug 59695 (the infamous laptop-killing bug), or rather, is the actual cause of the drive problem.
On my laptop, ACPID gets a battery event roughly every 15 seconds, each of these produces a write to the log file.
Laptop hard drives seem to be set up for bursty I/O (a reasonably assumption for general laptop usage), so their worst-case scenario is precisely this, a single write every 15 seconds. The laptop parks after 10 seconds of inactivity, then gets woken up about 5 seconds later, and this repeats continuously whenever the laptop is idle.
The simplest fix is to disable ACPID logging by adding "-l /dev/null" to the command line. Ultimately ACPID should be changed to only log errors and infrequent events.
This needs to be communicated upstream - it will happen on any distro that uses ACPID and lets it log its output. I've seen it on Debian, too.