[HEADS-UP] The systemd unit files I'll post

[Roberto Ragusa]

Till Maas wrote:
> On Thu, Jul 15, 2010 at 04:18:06PM +0200, Lennart Poettering wrote:
>> On Thu, 15.07.10 08:58, Till Maas (opensource at till.name) wrote:
>>
>>> On Thu, Jul 15, 2010 at 03:30:41AM +0200, Lennart Poettering wrote:
>>>
>>> And why should acpid go away? What is there that can be used instead?
>> Used for what exactly?
> 
> To react on ACPI events, e.g. when the lid of a notebook is opened[0]
> or when the notebook is removed from a docking station.
> 
>> upowerd handles this now.
> 
> It looks like it is as bad documented as hal. At least the manpages on
> freedesktop.org[1] did not provide any information about what one can do
> with it. Acpid has a very good manpage that shows how one can easily
> add scripts that react to any ACPI event.

I have a use case which does not involve power management.
Some keys on my Thinkpad generate ACPI events which I can assign
to scripts run by acpid.

For example the "ThinkVantage" button is mapped to 'sync' (acpid is
one of the things which manages to work even on a half-crashed system),
then I mapped some Fn-F[1-12] combinations to other system wide
functions. One is mapped to kill -STOP/-CONT all running firefox processes,
which I use to save battery while reading webpages, excluding the instants
when I scroll or change tab. Another one helps with the display brightness
control (detect brightness+ key -> run command to increase brightness).
Another one is used to activate the screensaver/screenlock when
walking away from the machine; maybe this one could have been done in a
session context, but Fn-F1 is really well positioned to be reached by
my fingers.

-- 
   Roberto Ragusa    mail at robertoragusa.it