The uacpid package

[Tags: bsd3, program]

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]


Versions0.0.2, 0.0.3, 0.0.4, 1.0.1,, 1.1, 1.2
Change logNone available
Dependenciesbase (>=3 && <5), containers, directory, filepath, hslogger, mtl, network, old-locale, process, regex-compat, time (<1.5), unix [details]
Copyright2009 Dino Morelli
AuthorDino Morelli
MaintainerDino Morelli <>
Home page
UploadedWed Jul 15 23:30:30 UTC 2009 by DinoMorelli
UpdatedTue Jun 30 01:56:16 UTC 2015 by AdamBergmark to revision 1
Downloads1132 total (13 in last 30 days)
0 []
StatusDocs not available [build log]
Last success reported on 2015-06-10 [all 5 reports]


Maintainers' corner

For package maintainers and hackage trustees

Readme for uacpid-0.0.2

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