also sprach Mattia Dongili <malattia@linux.it> [2006.01.12.1006 +0100]: > No. That's the kernel only supporting a single reader for > /proc/acpi/event. I'm cooking a patch to support multiple readers > (based on an old and never applied patch) but I doubt it will be > accepted mainline. /proc/acpi/event contention has _always_ been > a problem and the only solution is to support multiple readers, > not to require acpid's socket, that's just ridiculous :) Fully agreed. > I's actually just a matter of which process starts first: yes. > So, I'd say this is either an acpid bug (start earlier?) or better > yet a kernel bug. The first is only a solution if the other bug is fixed. Or else an APT upgrade of acpid will hose the system. If that was fixed, it should be fine. I start xdm at S01, so that's probably the problem. Cheers, -- .''`. martin f. krafft <madduck@debian.org> : :' : proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP (sub)keys? Use subkeys.pgp.net as keyserver! #define emacs eighty megabytes and constantly swapping.
Attachment:
signature.asc
Description: Digital signature (GPG/PGP)