On Wed, Nov 12, 2008, John Talbut wrote: > I have resolved my problem - I did not have /proc/acpi/event support > (config ACPI_PROC_EVENT) compiled into my kernel (as suggested by the > Debian supplied /usr/src/linux-source-2.6.26/drivers/acpi/Kconfig).
We could check for /proc/acpi/event before starting acpid, but as it's possible to override this pathname with acpid's -e flag, it would be hard to check whether the flag was passed or not. I can't really come up for a good reason to override this path; I don't think anybody has proc somewhere else, the relative /proc pathname is probably hardcoded in the kernel, so the only use case I can imagine would be some kind of event relay file. What do others think of testing for /proc/acpi/event (instead of /proc/acpi) at the top of acpid.init and exiting immediately with 0 if not present? (disabling acpid) -- Loïc Minier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
