battery-stats-collector - Collect statistics about battery charge
battery-stats-collector [option] ...
Does exactly as it says on the tin - it will collect information from
the APM subsystem and write it to a log file.
Normally battery-stats-collector will be invoked by the system startup
battery-stats follow the usual GNU command line syntax, with long
options starting with two dashes (‘-’).
Show version of battery-stats-collector and exit.
Show summary of options and exit.
Log error messages to syslog, rather than stderr. Note that
messages regarding invalid command line parameters will still go
-o filename, --output filename
Append statistics to the given file. The default filename is
Only collect a single sample and exit. The default is to loop
-i seconds, --interval=seconds
Sampling intervals in seconds. If not specified, stats will be
collected every 30 seconds.
Keeps quiet about missing batteries. This stops the warnings on
stderr/syslog that would otherwise occur when the battery is
-F samplecount, --flush=samplecount
Flushes data to the logfile every <samplecount> samples. A value
of zero turns off flushing altogether. If left unspecified,
battery-stats-collector will assume a value of 1, i.e. flush at
every write. Setting the value too low will tend to keep the
disk spinning (and use battery needlessly). Setting the value
too high will loose statistics in case of an improper shutdown.
Note that 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.
Default file for writing battery charge samples to.
Newer versions of this program may (or may not) be available at
This manual page was written by Karl E. Jørgensen <firstname.lastname@example.org>,
for the Debian GNU/Linux system (but may be used by others).
September 18, 2002