Marcus's analysis looks right to me:
> > But who can tell which is the grand-piece-of-sw that has the exclusive
> > right to open /proc/acpi/event?
> The one which has been designed to multiplex the events to make them
> available to other programs, and it's acpid.
The standard Debian setup is to
On Jan 23, Mattia Dongili <[EMAIL PROTECTED]> wrote:
> > to be fixed in X (I suggest by retrying to open the socket if it worked
> > the first time).
> this is exactely what the patch I submitted here does. But it does only
> once, so if the socket is not there on the first retry it'll steal
> /pr
On Sun, Jan 22, 2006 at 11:24:15PM +0100, Marco d'Itri wrote:
> On Jan 12, Mattia Dongili <[EMAIL PROTECTED]> wrote:
>
> > 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) b
On Jan 12, Mattia Dongili <[EMAIL PROTECTED]> wrote:
> 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 h
The problem is made worse by the fact that /etc/logrotate.d/acpid
contains:
postrotate
/etc/init.d/acpid restart >/dev/null
at which point X will lose the acpid socket connection and grab the
/proc/acpi/event node instead and acpid will fail to restart.
--
To UNSUBSCRIBE, email to [
On Thu, Jan 12, 2006 at 07:34:46PM +0100, Frans Pop wrote:
> On Thursday 12 January 2006 10:06, Mattia Dongili wrote:
> > no, 345537 only fixed a bug, xorg was already trying to read acpi
> > events. I's actually just a matter of which process starts first:
> > - acpid: xorgs opens acpid's socket a
On Thursday 12 January 2006 10:06, Mattia Dongili wrote:
> no, 345537 only fixed a bug, xorg was already trying to read acpi
> events. I's actually just a matter of which process starts first:
> - acpid: xorgs opens acpid's socket and we all are happy
Does this still work when acpid has to be temp
also sprach Mattia Dongili <[EMAIL PROTECTED]> [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/
On Thu, January 12, 2006 1:59 am, martin f krafft said:
> Package: xserver-xorg
> Version: 6.9.0.dfsg.1-3
> Severity: important
>
> If Xorg is running, it claims /proc/acpi/events. This causes acpid
> to not start:
>
> lapse:~# /usr/sbin/acpid -c /etc/acpi/events -s /var/run/acpid.socket
> acpid: c
Package: xserver-xorg
Version: 6.9.0.dfsg.1-3
Severity: important
If Xorg is running, it claims /proc/acpi/events. This causes acpid
to not start:
lapse:~# /usr/sbin/acpid -c /etc/acpi/events -s /var/run/acpid.socket
acpid: can't open /proc/acpi/event: Device or resource busy
Either require acpi
10 matches
Mail list logo
