Approximately every second the pm-utils scripts write this junk to my
/var/log/pm-powersave.log file:

=============8<-----------------------------
Running hook /usr/lib/pm-utils/power.d/95hdparm-apm true:
/usr/lib/pm-utils/power.d/95hdparm-apm true: success.

Running hook /usr/lib/pm-utils/power.d/anacron true:
/usr/lib/pm-utils/power.d/anacron true: success.

Running hook /usr/lib/pm-utils/power.d/disable_wol true:
Setting Wake On Lan for eth0 to disable...Done.
/usr/lib/pm-utils/power.d/disable_wol true: success.

Running hook /usr/lib/pm-utils/power.d/intel-audio-powersave true:
Setting power savings for snd_hda_intel to 1...Done.
/usr/lib/pm-utils/power.d/intel-audio-powersave true: success.

Running hook /usr/lib/pm-utils/power.d/laptop-mode true:
Laptop mode enabled.
/usr/lib/pm-utils/power.d/laptop-mode true: success.

Running hook /usr/lib/pm-utils/power.d/pci_devices true:
Setting Host Bridge 0000:00:00.0 to auto
Setting Audio device 0000:00:03.0 to auto
Setting Ethernet device 0000:00:19.0 to auto
Setting Audio device 0000:00:1b.0 to auto
Setting Wireless device 0000:02:00.0 to auto
/usr/lib/pm-utils/power.d/pci_devices true: success.

Running hook /usr/lib/pm-utils/power.d/pcie_aspm true:
sh: echo: I/O error
/usr/lib/pm-utils/power.d/pcie_aspm true: success.

Running hook /usr/lib/pm-utils/power.d/sata_alpm true:
/usr/lib/pm-utils/power.d/sata_alpm true: success.

Running hook /usr/lib/pm-utils/power.d/sched-powersave true:
**sched policy powersave ON
/usr/lib/pm-utils/power.d/sched-powersave true: success.

Running hook /usr/lib/pm-utils/power.d/usb_bluetooth true:
Setting /sys/bus/usb/devices/1-8 to auto
/usr/lib/pm-utils/power.d/usb_bluetooth true: success.

Running hook /usr/lib/pm-utils/power.d/wireless true:
cat: /sys/class/net/wlan0/device/enabled: No such file or directory
/usr/lib/pm-utils/power.d/wireless true: success.

Running hook /usr/lib/pm-utils/power.d/xfs_buffer true:
/usr/lib/pm-utils/power.d/xfs_buffer true: not applicable.
-------------------------->8=======================


This creates log files that quickly grow to many gigabytes.  Last I
checked, the log file was at 23GB on a 37GB root partition.  Since
logrotate is used to rotate these logs (and logrotate is a amateur-ish
hack that doesn't rotate logs in real-time like daemontools or runit),
the files can easily grow too large for the partition with no
monitoring.

So there are multiple problmes here in design and implementation:

A. Something is causing events to be generated every second.  I don't
know what that is.  Is this normal?

B. The logs are too verbose by default, but don't really help a normal
person understand what is going on.

C. The logs don't have any timestamps associated with them.
Distinctly unhelpful.

D. The logs don't rotate off in a sane way, based on a fixed size or
other metric that prevents pm-utils from DoSing the system.  Try
runit's svlogd.


All of this churning every second not only wastes my disk space, but
it also burns precious battery life and degrades the life of my SSD.
Isn't the point of something like pm-utils and "powersave" mode
supposed to work in the opposite direction?  Hence the "important"
rating for a package of this kind.

Thanks,
tim

Dear submitter,

as the package pm-utils has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1058701

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)