403Webshell
Server IP : 23.254.227.96  /  Your IP : 216.73.216.46
Web Server : Apache/2.4.62 (Unix) OpenSSL/1.1.1k
System : Linux hwsrv-1277026.hostwindsdns.com 4.18.0-477.13.1.el8_8.x86_64 #1 SMP Tue May 30 14:53:41 EDT 2023 x86_64
User : viralblo ( 1001)
PHP Version : 8.1.31
Disable Function : NONE
MySQL : OFF  |  cURL : ON  |  WGET : ON  |  Perl : ON  |  Python : OFF  |  Sudo : ON  |  Pkexec : ON
Directory :  /proc/self/root/usr/share/doc/acpid/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :


[ Back ]     

Current File : /proc/self/root/usr/share/doc/acpid/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.

Youez - 2016 - github.com/yon3zu
LinuXploit