When running sys-apps/baselayout-2.0.0_alpha2, sys-power/acpid-1.0.4-r5 is unable to start because it cannot read /proc/acpi/event. Here's the actual error message: $ /etc/init.d/acpid start * Starting acpid ... acpid: can't open /proc/acpi/event: Device or resource busy * start-stop-daemon: failed to started `/usr/sbin/acpid' [ !! ] * ERROR: acpid failed to start Reproducible: Always Steps to Reproduce: 1. Install sys-apps/baselayout-2.0.0_alpha2 and sys-power/acpid-1.0.4-r5. 2. Reboot the system. 3. Try to start /etc/init.d/acpid Actual Results: acpid fails to start because it cannot read the necessary file under /proc/acpi. Expected Results: acpid should be able to read the file and start correctly. Trying to less/cat /proc/acpi/event manually gives a "Device or resource busy" error message.
Please post output of ps -p$(fuser /proc/acpi/event 2>/dev/null) -f
(In reply to comment #1) > Please post output of > ps -p$(fuser /proc/acpi/event 2>/dev/null) -f > $ ps -p$(fuser /proc/acpi/event 2>/dev/null) -f UID PID PPID C STIME TTY TIME CMD 102 3885 3874 0 14:53 ? 00:00:00 hald-addon-acpi: listening on acpi kernel interface /proc/acpi/event Well, it seems like I was a bit hasty when blaiming baselayout for the malfunctioning acpid. Sorry for that.
By the way, now that the bug has been reassigned, I'll give some additional information. I'm currently running sys-apps/hal-0.5.9-r1 .
acpid needs to be added PROPERLY to your current runlevel. If you're attempting to start up acpid AFTER HAL, then either you don't have acpid in the same runlevel as HAL or you're just plain doing something wrong. Add them both to the same runlevel and baselayout will take care of everything else, since hald initscript is marked "uses acpid".
Doug: What? So .. what's the proper way to 'fix' this, as far as I know only 1 device is allowed to open /proc/acpi/event and this will either be acpid or hald. I reccon we'd be moving to having everything handled by hald, thus we need a deamon/feature of some sort that deals with things like power button pressed? Is acpid even needed with hald controlling acpi events?
Some people still use acpid for certain functionality that HAL does not provide. This issue is a non-issue as it's a configuration issue. You need to stick hal and acpid both in the default runlevel and baselayout will take care of the rest.
