BLACKSITE
:
216.73.217.173
:
119.18.54.19 / www.yugtechnologies.com
:
Linux sh200.bigrock.com 4.19.286-203.ELK.el7.x86_64 #1 SMP Wed Jun 14 04:33:55 CDT 2023 x86_64
:
/
usr
/
share
/
doc
/
acpid-2.0.19
/
Upload File:
files >> //usr/share/doc/acpid-2.0.19/TODO
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.