BATTERY-STATS-COLLECTOR(8)
π BATTERY-STATS-COLLECTOR(8) π
okay bestie, so this is a page from the System Manager's Manual, and it's all about a lil tool called battery-stats-collector β yes that's section 8, the big-girl admin section, we love that for her π
β¨ NAME β¨
battery-stats-collector β literally just collects stats about battery charge π
πΈ SYNOPSIS πΈ
battery-stats-collector [option] ...
π¦ DESCRIPTION π¦
She does exactly what it says on the tin, no cap. It pulls info from the APM subsystem and writes it into a log file. That's the whole vibe. π
Normally? battery-stats-collector gets invoked by the system startup scripts, like she's got places to be at boot time. main character energy fr fr.
π OPTIONS π
battery-stats follow the usual GNU command line syntax, with long options starting with two dashes (-).
-o FILE,--output FILEβ appends the statistics to FILE. The default filename is/var/log/battery-statsπΎ-i SECS,--interval=SECSβ sampling interval, in seconds. If you don't say anything, stats get collected every 30 seconds β°-F COUNT,--flush=COUNTβ flushes data to the log file every COUNT samples. A value of zero turns flushing off entirely. If you leave it unspecified,battery-stats-collectorassumes a value of 1, aka flush at every single write. π½
real talk: set it too low and you'll keep the disk spinning (and burn battery for absolutely no reason π). Set it too high and you'll lose statistics if the shutdown is improper. it's giving β¨tradeoffsβ¨
Also note: since battery-stats-collector uses the standard Ansi C library, data will still be flushed periodically (regardless of this setting) once the buffer fills up. The size of the buffer is platform dependent, but 4Kb and 8Kb seem pretty normal.
-b NUM,--battery-num=NUMβ read information about battery number NUM. for when you've got multiple batteries installed, look at you, so fancy ππ-1,--onceβ only collect a single sample and then exit. The default is to loop continiously. π-I,--ignore-missing-batteryβ keeps quiet about missing batteries. This stops the warnings onstderr/syslogthat would otherwise show up when the battery is missing. π€«-s,--syslogβ log error messages to syslog, rather than tostderr. Heads up tho: messages about invalid command line parameters will still go tostderr. π-V,--versionβ show version ofbattery-stats-collectorand exit. βοΈ-h,--helpβ show summary of options and exit. the girl loves to explain herself π
π FILES π
/var/log/battery-statsβ the default file for writing battery charge samples to. ποΈ
π SEE ALSO π
Newer versions of this program may (or may not) be available at http://karl.jorgensen.com/battery-stats β lowkey iconic that they said "or may not" π
π AUTHOR π
This manual page was written initially written by Karl E. Jorgensen <karl@jorgensen.com>, for the Debian GNU/Linux system (but may be used by others).
Adapted by Antonio Radici <antonio@dyne.org> to include libacpi and autotools support, see History for details.
Kevin Funk <kevin@kfunk.org> took over maintainership in 2012. π
so yeah, that's the whole page, we ate and left no crumbs. this was battery-stats-collector(8) from the System Manager's Manual, dated October 30, 2012 β hope your battery stats are immaculate, bestie, ily π«Άπβ¨
π¦ where this page comes from
- debian bookworm: battery-stats 0.5.6-2+b2 Β· GPL-2.0-or-later
- debian trixie: battery-stats 0.5.6-2.1 Β· GPL-2.0-or-later
- ubuntu jammy: battery-stats 0.5.6-2 Β· GPL-2.0-or-later
- ubuntu noble: battery-stats 0.5.6-2.1 Β· GPL-2.0-or-later
- ubuntu resolute: battery-stats 0.5.6-3 Β· GPL-2.0-or-later
- ubuntu stonking: battery-stats 0.5.6-3 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms