uacpid: Userspace Advanced Configuration and Power Interface event daemon

[ bsd3, program, system ] [ Propose Tags ]

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.

[Skip to Readme]
Versions 0.0.2, 0.0.3, 0.0.4, 1.0.1,, 1.1, 1.2
Dependencies base (>=3 && <5), containers, directory, filepath, hslogger, mtl, network, old-locale, process, regex-compat, time (<1.5), unix [details]
License BSD-3-Clause
Copyright 2009 Dino Morelli
Author Dino Morelli
Maintainer Dino Morelli <>
Revised Revision 1 made by AdamBergmark at Tue Jun 30 01:56:16 UTC 2015
Category System
Home page
Uploaded by DinoMorelli at Wed Jul 15 23:30:30 UTC 2009
Distributions NixOS:1.2
Executables uacpid
Downloads 3047 total (22 in the last 30 days)
Rating (no votes yet) [estimated by rule of succession]
Your Rating
  • λ
  • λ
  • λ
Status Docs not available [build log]
Last success reported on 2015-06-10 [all 7 reports]
Hackage Matrix CI


Note: This package has metadata revisions in the cabal description newer than included in the tarball. To unpack the package including the revisions, use 'cabal get'.

Maintainer's Corner

For package maintainers and hackage trustees

Readme for uacpid-0.0.2

[back to package description]
Getting started developing:

In order for the conf file code to work correctly in a development setting, what you should do is:

   $ runhaskell Setup.hs configure --prefix=foo

Where foo is some scratch development installation dir, doesn't really matter where.

You must then runhaskell Setup.hs install to copy files there. After which, running will be able to locate default conf which will then allow it to bootstrap the "real" configuration.

Running the daemon in a development setting:

Start this daemon with the helper script in bin/uacpid-dev
This will use a custom HOME environment that points to dev/home/
And will keep it from looking at your real $HOME/.uacpid/

Start in developement like this:
   $ bin/uacpid-dev &

Stop in developement like this, use the full path so only the development execution is killed. Or get the pid and use kill:
   $ killall dist/build/uacpid/uacpid