This bug was fixed in the package powernap - 2.1-0ubuntu1 --------------- powernap (2.1-0ubuntu1) natty; urgency=low
[ Andres Rodriguez ] * config: - Default ACTION to pm-powersave instead of best-effort. - Enable WoLMonitor and ConsoleMonitor by default - Disable ProcessMonitor by default. - Change powersave defaults to 0 instead of 4. Update related files. * powernap/monitors: - Rename RemoteMonitor to UDPMonitor. - Add WoLMonitor and support to run it. - Add ConsoleMonitor and support to run it. * powernap/powernap.py: - Improve config loading method for Monitors. * sbin/powernapd: Change approach of powernapd_loop. - GRACE period is time between ABSENT_SECONDS and (ABSENT_SECONDS - GRACE_SECONDS) - Only send a Wall message when on GRACE Period. - Enable Monitors to run at all times. Specifically when in PowerSave. * man/powernapd.8: Update to list available Monitors with description. * Update Copyright years/email in some of the files. [ Dustin Kirkland ] * config, powernap/monitors/TCPMonitor.py, powernap/powernap.py: - add a TCP Monitor * config, powernap/monitors/LoadMonitor.py, powernap/powernap.py: - add a system Load Monitor * debian/control: bump standards version * debian/rules: make sure powernapd starts on install, LP: #705959 * config: update service restart method -- Andres Rodriguez <andres...@ubuntu.com> Wed, 26 Jan 2011 14:16:31 -0500 ** Changed in: powernap (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/705959 Title: powernapd not running after install -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs