Linux server2.hpierson.com 3.10.0-1160.105.1.el7.x86_64 #1 SMP Thu Dec 7 15:39:45 UTC 2023 x86_64
Apache
: 162.0.216.123 | : 216.73.216.152
28 Domain
?7.4.33
yvffpqmy
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
README
+ Create Folder
+ Create File
/
usr /
share /
doc /
acpid-2.0.19 /
[ HOME SHELL ]
Name
Size
Permission
Action
COPYING
17.56
KB
-rw-r--r--
Changelog
21.03
KB
-rw-r--r--
README
3.87
KB
-rw-r--r--
TESTPLAN
3.52
KB
-rw-r--r--
TODO
1.26
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : 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.
Close