Re: pmud deamon problem

[Michael Schmitz <schmitz@mail.biophys.uni-duesseldorf.de>]

> pmud[589]: pmud [threshold = 420, margin = 15] started
> pmud[589]: opening /dev/adb
> pmud[589]: opening /dev/pmu
> pmud[589]: bind socket
> pmud[589]: daemon stopped (bind socket)
>
> does anybody know what the reason for this is?

Depends what's in your /etc/default/power: with the -u flag there, pmud
will attempt to open a unix domain socket /etc/power/control to accept
commands (without -u, commands are read via TCP/IP). After opening the
socket (or TCP/IP port), pmud binds to the socket in order to receive any
data sent there. The message 'bind socket' means this bind failed. The
'daemon stopped' just means pmud gave up (because of the fatal bind
error).

If you recently upgraded the kernel and the new kernel no longer supports
unix domain sockets, the bind syscall would naturally fail. Another reason
might be a stale control socket (but there's code to remove leftover
sockets before opening a new one, in theory). Check if /etc/power/control
is present before starting pmud, and remove it if it's there.

	Michael