On Thu, Nov 13, 2008 at 06:40:21PM +0100, Loïc Minier wrote: > 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
Even if they had our current test would fail as well. > probably hardcoded in the kernel, so the only use case I can imagine > would be some kind of event relay file. But even then the file /proc/acpi/event would exists as the base for the event relaying, right? > 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) Makes sense IMO. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
