<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to feature-requests</title><link href="https://sourceforge.net/p/acpid/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/acpid/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/acpid/feature-requests/</id><updated>2009-10-19T16:20:37Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>Support for arbitrary input events</title><link href="https://sourceforge.net/p/acpid/feature-requests/7/" rel="alternate"/><published>2009-10-19T16:20:37Z</published><updated>2009-10-19T16:20:37Z</updated><author><name/><uri>https://sourceforge.net</uri></author><id>https://sourceforge.net9c9ccaf756f50a69cb0dc398a58639a7d12b6b5b</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Acpid currently only defines a handful of button input events. See the Debian bug report &lt;a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=521280." rel="nofollow"&gt;http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=521280.&lt;/a&gt; &lt;/p&gt;
&lt;p&gt;I think a better solution would be, to support arbitrary events. Just listen to all events, that are defined in an event file. A special syntax would be needed. E.g.: `event=button/&amp;lt;type&amp;gt;/&amp;lt;code&amp;gt;/&amp;lt;value&amp;gt;'. So to listen to the power button, one would write `event=button/EV_KEY/KEY_POWER/1'.&lt;/p&gt;
&lt;p&gt;Type, code and value can easily be found by `input-events'. Acpid would parse all event files, and then simply listen to all found button events. No need for users to wait until acpid supports a certain event. There would need to be a mapping from the names (e.g. EV_KEY) to their integer values. This mapping should be in a separate text file, with `name=value' entries. Acpid would parse this file on start-up. It can be generated automatically from input.h. The advantage would be, that acpid was rather independent of kernel changes.&lt;/p&gt;
&lt;p&gt;I guess I could write a patch for acpid, if that was appreciated. But the event syntax would have to be agreed upon.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Should check for HAL "button" property</title><link href="https://sourceforge.net/p/acpid/feature-requests/6/" rel="alternate"/><published>2009-04-27T14:12:44Z</published><updated>2009-04-27T14:12:44Z</updated><author><name>Tony Houghton</name><uri>https://sourceforge.net/u/realh/</uri></author><id>https://sourceforge.neta435f7fd1789d1afdfbe152276b263a3c9ca680e</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I've got a remote control attached to my DVB card and it works as an input device. Recently it started shutting down the PC when I pressed the remote's power button. I thought I should be able to prevent this without also disabling the case's power button by removing the "button" property from "info.capabilities" in a HAL FDI file, but although hal-device shows that I've removed the property successfully, it didn't make any difference to the behaviour so I had to disable all power buttons in acpid.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Add a quiet mode for logging</title><link href="https://sourceforge.net/p/acpid/feature-requests/5/" rel="alternate"/><published>2007-09-02T18:37:30Z</published><updated>2007-09-02T18:37:30Z</updated><author><name>Bill sharer</name><uri>https://sourceforge.net/u/bsharer/</uri></author><id>https://sourceforge.netc053e9f81fbc18b1346a9df01b79767fe95f5094</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I'm currently using acpid on an HP Turion ML40 based laptop under gentoo as the acpid-1.0.6 ebuild.  This uses the apcid-1.0.6.tar.gz tarball as is without any patches.&lt;/p&gt;
&lt;p&gt;I'm not sure if this is a quirk of the ML40, but acpid handles a CPU0 processor event on the order of one every second or more.  This results in about 3 LOG_INFO level messages going to the syslog, and the current software doesn't allow the logging level to be turned off or tuned.&lt;/p&gt;
&lt;p&gt;The resulting datastorm rapidly fills both /var/log/syslog and /var/log/messages and prevents any sort of battery mode conservation by spinning down the hard drive.&lt;/p&gt;
&lt;p&gt;I've hacked my config as follows in order to provide a new q switch for quiet mode that only logs LOG_NOTICE or lower when enabled.  I've also changed a couple of logging calls from LOG_INFO to LOG_NOTICE so that they would still appear.  Logging runs as before if the switch is not supplied on startup.&lt;/p&gt;
&lt;p&gt;I actually think that LOG_INFO level reports from events should be removed in favor of having the user do something with the triggers and scripts in /etc/acpid instead, but I guess you wouldn't see what a CLIENT may be up to.&lt;/p&gt;
&lt;p&gt;----------------------&lt;/p&gt;
&lt;p&gt;diffs to acpid.c&lt;/p&gt;
&lt;p&gt;58a59&lt;br /&gt;
&amp;gt; static int quiet = 0;&lt;br /&gt;
161c162,163&lt;br /&gt;
&amp;lt;       acpid_log(LOG_INFO, "starting up\n");&lt;br /&gt;
---&lt;br /&gt;
&amp;gt;       acpid_log(LOG_NOTICE, "starting up\n");&lt;br /&gt;
&amp;gt;       if (quiet) acpid_log(LOG_NOTICE, "starting in quiet mode\n");&lt;br /&gt;
272a275&lt;br /&gt;
&amp;gt;               {"quiet", 0, 0, 'q'},&lt;br /&gt;
297c300&lt;br /&gt;
&amp;lt;               i = getopt_long(*argc, *argv, "c:de:fg:m:s:Svh", opts, NULL);&lt;br /&gt;
---&lt;br /&gt;
&amp;gt;               i = getopt_long(*argc, *argv, "c:de:fg:m:q:s:Svh", opts, NULL);&lt;br /&gt;
320a324,326&lt;br /&gt;
&amp;gt;               case 'q':&lt;br /&gt;
&amp;gt;                       quiet = 1;&lt;br /&gt;
&amp;gt;                       break;&lt;br /&gt;
456c462,463&lt;br /&gt;
&amp;lt;       vsyslog(level, fmt, args);&lt;br /&gt;
---&lt;br /&gt;
&amp;gt;       if ((level &amp;lt; LOG_INFO) || (!quiet))&lt;br /&gt;
&amp;gt;               vsyslog(level, fmt, args);&lt;/p&gt;
&lt;p&gt;------------------&lt;/p&gt;
&lt;p&gt;diffs to event.c&lt;/p&gt;
&lt;p&gt;157c157&lt;br /&gt;
&amp;lt;       acpid_log(LOG_INFO, "%d rule%s loaded\n",&lt;br /&gt;
---&lt;br /&gt;
&amp;gt;       acpid_log(LOG_NOTICE, "%d rule%s loaded\n",&lt;br /&gt;
343c343&lt;br /&gt;
&amp;lt;       acpid_log(LOG_INFO, "%d client rule%s loaded\n",&lt;br /&gt;
---&lt;br /&gt;
&amp;gt;       acpid_log(LOG_NOTICE, "%d client rule%s loaded\n"&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>logging via syslog</title><link href="https://sourceforge.net/p/acpid/feature-requests/4/" rel="alternate"/><published>2007-06-12T21:32:17Z</published><updated>2007-06-12T21:32:17Z</updated><author><name>Matěj Laitl</name><uri>https://sourceforge.net/u/strohel/</uri></author><id>https://sourceforge.netf793c265816e2a345e9020fd75bcdb55a000e778</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Summary said that, please implement logging via syslog facility. It's much more flexible and will make many things easier. (/me logs to disk when on ac, to /dev/tty12 when on battery)&lt;/p&gt;
&lt;p&gt;Best regards, strohel&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Less log chatter</title><link href="https://sourceforge.net/p/acpid/feature-requests/3/" rel="alternate"/><published>2004-04-07T09:12:28Z</published><updated>2004-04-07T09:12:28Z</updated><author><name>Jason Marshall</name><uri>https://sourceforge.net/u/jdmarshall/</uri></author><id>https://sourceforge.net6a7321ffa44b8261cfb601b1b8ba0acfc90d06d3</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;When run without parameters, the number of messages&lt;br /&gt;
sent to the logs seems to be excessive.  The most&lt;br /&gt;
noteworthy case is that of the battery charge state,&lt;br /&gt;
which seems to be the most prolific of the events I've&lt;br /&gt;
witnessed.  The tragedy here is that these events are&lt;br /&gt;
logged at the worst possible time: when the device is&lt;br /&gt;
on a power budget, and likely trying to avoid excessive&lt;br /&gt;
disk accesses. &lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>RFE: --do-not-fork option</title><link href="https://sourceforge.net/p/acpid/feature-requests/2/" rel="alternate"/><published>2003-08-18T20:37:46Z</published><updated>2003-08-18T20:37:46Z</updated><author><name>Enrico Scholz</name><uri>https://sourceforge.net/u/ensc/</uri></author><id>https://sourceforge.net6aec235a9e1eac18465bf2dd00d0137723ae490d</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;It would be nice when acpid has an option which lets it&lt;br /&gt;
operate normally but prevents its forking into&lt;br /&gt;
background. This is required since advanced&lt;br /&gt;
init-concepts like minit and djb's supervise (which are&lt;br /&gt;
e.g. respawning died processes automatically), need&lt;br /&gt;
hacks to work with programs going into background.&lt;/p&gt;
&lt;p&gt;Such an option could operatore similarly to '-d', but&lt;br /&gt;
without its debugging aspects (e.g. logging to&lt;br /&gt;
stdout/stderr instead of a file).&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>CPU Load</title><link href="https://sourceforge.net/p/acpid/feature-requests/1/" rel="alternate"/><published>2003-04-11T10:54:15Z</published><updated>2003-04-11T10:54:15Z</updated><author><name>Christian Berg</name><uri>https://sourceforge.net/u/x-eniac/</uri></author><id>https://sourceforge.net3d8ce71f777763fd57397854ec6acdf6b5f2d82e</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Is it possible that ACPID also watches the CPU Load?&lt;br /&gt;
This would be nice for the SpeedStep Processors.&lt;br /&gt;
Less then 10% load average = throttle down the CPU and&lt;br /&gt;
save some battery.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>