On Mon, Sep 04, 2006 at 04:57:54PM +0200, martin f krafft wrote:
> also sprach Sjoerd Simons <[EMAIL PROTECTED]> [2006.09.04.1622 +0200]:
> > It already does that, it first tries the proc interface, then the socket.
> > The
> > problem is that afaik /var/run might be empty on boot, so checking for
> > /var/run/acpid.socket then doesn't really help.
>
> It should first try the socket, then /proc. And we just have to make
> sure that acpid starts before hald. Then, if the socket is present,
> hal knows what to do.
It doesn't matter if it does:
* Try to grab the proc interface
* If successfull then use that, otherwise acpid must have it so use it's
socket.
Or:
* Try to open the socket
* If it fails then there is no acpid, so try the proc interface.
Both will work right iff apcid is started first. Which is even the
case on boot (As S20acpid is started before S20dbus).
The problem for users appears when either hald is already running and acpid is
freshly installed or when both are stopped for an upgrade and hal is started
first. My proposed solution (check for the acpid binary) will solve the second
case, i can't really fix the first.
Sjoerd
--
If you refuse to accept anything but the best you very often get it.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
