On Wed, Nov 05, 2014 at 06:36:47AM -0800, Josh Triplett wrote: > If acpid needs to run to manage scripts in /etc/acpi/events/, then in > addition to the acpid.socket file, you should also ship an acpid.path > file, containing: > > [Path] > ConditionDirectoryNotEmpty=/etc/acpi/events/ > > [Install] > WantedBy=paths.target > > That will then cause systemd to automatically activate acpid.service > whenever /etc/acpi/events/ becomes non-empty, in addition to > acpid.socket which will activate acpid.service whenever anything > connects to the acpid socket.
Interesting, I didn't know this feature so far. However, I don't think this makes sense because acpid comes with a set of pre-defined events in /etc/apci/events or in other words, the only way to get it empty is to remove those by hand. And why should you? 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 Jabber: michael.meskes at gmail dot com VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
