Hi There must be something wrong with the configure flags of hal-0.5.5.1. No matter whether you compile it with acpi USE flag on or off it keeps saying addon-acpi.c:78: Cannot connect to acpid socket: No such file or directory This error doesn't show up when you have acpid installed, but I have not. greetings fabian
*** This bug has been marked as a duplicate of 107211 ***
This is no duplicate of the other bug. It's a problem with the configure script of hal. There is no "--enable-acpi-proc" in the configure script, altough it's used in the ebuild but a "--disable-acpi-proc" option, and you need "--disable-acpi-acpid" if you want to run hal without acpid.
Just live with the error message for now. It's nothing fatal. Your choice is to have ACPID installed or the prefered way of reading /proc/acpi/event directly. Which is basically what acpid does. In the future acpid will go away and hal will take over the responsiblity. There are however some people, like me, that need acpid because HAL doesn't provide all the functionality yet. So we're saying "enable acpi proc" in the configure command, even though upstream's configure command just ignores this and enables it no matter what. We're not saying "disable acpid" because then HAL wouldn't work for people like me. So it's just an error message to live with, your system is still connecting to /proc/acpi/event and running fine. There is no 30 second polling delay for using /proc/acpi/event instead of acpid because acpid just reads /proc/acpi/event just like HAL reads it. But then it broadcasts those messages out across the socket to any listening app. That's why it seems different as far as time delay for messages. Now I know you know all this Fabian, since we discussed this with upstream on the mailing list. Just including this here for other developer's sake. And yes, you're right... there was a permissions issue on /proc/acpi/event with the -r2 release, that's why there is -r3.
So, I'm seeing this in sys-apps/hal-0.5.13-r2 filling up my /var partition with this line every 5 seconds: Jun 16 18:00:10 [hald-addon-acpi] [5790]: 18:00:10.973 [E] addon-acpi.c:83: Cannot connect to acpid socket: No such file or directory_ Jun 16 18:00:15 [hald-addon-acpi] [5790]: 18:00:15.973 [E] addon-acpi.c:83: Cannot connect to acpid socket: No such file or directory_ Jun 16 18:00:20 [hald-addon-acpi] [5790]: 18:00:20.973 [E] addon-acpi.c:83: Cannot connect to acpid socket: No such file or directory_ Jun 16 18:00:25 [hald-addon-acpi] [5790]: 18:00:25.973 [E] addon-acpi.c:83: Cannot connect to acpid socket: No such file or directory_ Jun 16 18:00:30 [hald-addon-acpi] [5790]: 18:00:30.973 [E] addon-acpi.c:83: Cannot connect to acpid socket: No such file or directory_ How do I get rid of it? "Just live with it" filling up /var is unacceptable, also it inteferes with diagnosing other programs. HAL has sucked since day one, and this is just another example, but that's not a reason to not fix it: it is a call to the HAL people to get their act together and take bugs like this seriously. How do I get my logs back?
I get rid of this messages by upgrading acpid from version 1 to version 2.
