Package: wmmoonclock
Version: 1.27-22
Severity: normal

I just ran powertop on my laptop, and found wmmoonclock is the program
that causes the CPU to wake up most often on my system.  If I am
understanding this strace correctly, it's sleeping for only 10ms at a
time, and hence wakes up 100 times a second.  Is it necessary to
update so often just to update the moon's phase?  If you need to poll
for mouse clicks in this time, 10 times a second would be plenty
(that's how often we update the telescope encoders and button presses
in the computer in the 3.9M AAT :-)

ioctl(3, FIONREAD, [0])                 = 0
ioctl(3, FIONREAD, [0])                 = 0
write(3, ">\2\7\0\1\0\200\7\4\0\200\7\5\0\200\7\0\0\0\0\0\0\0\0\205"..., 28) = 
28
nanosleep({0, 10000000}, NULL)          = 0
write(3, ">\2\7\0\1\0\200\7\3\0\200\7\5\0\200\7\0\0\0\0\0\0\0\0\205"..., 28) = 
28
ioctl(3, FIONREAD, [0])                 = 0
ioctl(3, FIONREAD, [0])                 = 0
ioctl(3, FIONREAD, [0])                 = 0
write(3, ">\2\7\0\1\0\200\7\4\0\200\7\5\0\200\7\0\0\0\0\0\0\0\0\205"..., 28) = 
28
nanosleep({0, 10000000}, NULL)          = 0
write(3, ">\2\7\0\1\0\200\7\3\0\200\7\5\0\200\7\0\0\0\0\0\0\0\0\205"..., 28) = 
28


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-1-686 (SMP w/1 CPU core)
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages wmmoonclock depends on:
ii  libc6                         2.6.1-1+b1 GNU C Library: Shared libraries
ii  libx11-6                      2:1.0.3-7  X11 client-side library
ii  libxext6                      1:1.0.3-2  X11 miscellaneous extension librar
ii  libxpm4                       1:3.5.7-1  X11 pixmap library

wmmoonclock recommends no packages.

-- debconf information:
* wmmoonclock/latitude: -37.833
* wmmoonclock/longitude: -145.033


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to