Userspace Advanced Configuration and Power Interface event daemon http://hub.darcs.net/dino/uacpid
|Latest on Hackage:||1.2|
This package is not currently in any snapshots. If you're interested in using it, we recommend adding it to Stackage Nightly. Doing so will make builds more reliable, and allow stackage.org to host generated Haddocks.
Userspace Advanced Configuration and Power Interface event daemon (Haskell)
uacpid is a daemon designed to be run in userspace that will monitor the local system's acpid socket for hardware events. These events can then be acted upon by handlers with access to the user's environment.
An example of why you need this: Suppose you want to have a hardware event change the active X displays, like a laptop external monitor function button. Some tools to achieve this display change require the logged in user's DISPLAY and other settings that may be difficult or impossible to gain access to from acpid scripts.
Another example is media control function buttons, like play/pause or next/previous track for a music player.
uacpid is running as you and is getting the hardware events reported by the system's acpid. uacpid can then act on the events on your behalf, with your environment.
uacpid will respond to SIGHUP by reloading the event handlers and reestablishing its connection to the acpid socket. Changes to the config file will require that uacpid be restarted, it will not reload the config on SIGHUP.
Handler syntax closely follows that of acpid. Users familiar with acpid should have no problem here. An example is included.
Note that uacpid requires acpid. It must be installed and running.
(Please see the uacpid man page for more detailed info)
- Download the cabalized source package from Hackage
- epub-tools is available for Arch Linux from the AUR
- Get the source with darcs:
$ darcs get http://hub.darcs.net/dino/uacpid
- If you're just looking, browse the source
Getting started developing:
This daemon is designed to make files for itself in ~/.uacpid/ the first time it's run. To assist with development, there is a script which will build a development installation and execution environment in /tmp/uacpid-dev/ for you.
To initialize for development:
Once that's completed, it can be run like this:
And once you have it, building the usual way:
$ cabal configure $ cabal build $ cabal install
Build and install with cabal-install:
$ cabal update ; cabal install uacpid
Dino Morelli <firstname.lastname@example.org>
- Added a lower bound for mtl dep
- Simplified some config error handling
- Decided to not force time >= 1.5 for now
- Reformatted cabal file a bit
- Replaced deprecated Control.Monad.ErrorT with ExceptT
- Fixed defaultTimeLocale import problem
- Now getting version from cabal info using Paths_ code
- Updated cabal info
- Moved copyright date up to 2015
- Adjustments to documentation
- Fixed code that was leaving zombie child processes by not waiting for them
- Changed listenAcpi delay time from 0.25 secs to 2 secs
- Refined developer and testing environment creation scripts
- Updated and clarified some documentation
- Fix for a recent change in how System.Directory.doesFileExist behaves with sockets
- Fixes for new GHC 6.12.x unused do binding warnings
- Various cosmetic changes of copyright dates and version strings
- Added HCAR info
Another try at fixing the broken man page installation problem on Arch Linux.
Fix for installation problem on Arch Linux. The man page was not getting installed.
- Initial release