__ __ __ __ _____ _ _ _____ _ _ _
| \/ | \ \ / / | __ \ (_) | | / ____| | | | |
| \ / |_ __\ V / | |__) | __ ___ ____ _| |_ ___ | (___ | |__ ___| | |
| |\/| | '__|> < | ___/ '__| \ \ / / _` | __/ _ \ \___ \| '_ \ / _ \ | |
| | | | |_ / . \ | | | | | |\ V / (_| | || __/ ____) | | | | __/ | |
|_| |_|_(_)_/ \_\ |_| |_| |_| \_/ \__,_|\__\___| |_____/|_| |_|\___V 2.1
if you need WebShell for Seo everyday contact me on Telegram
Telegram Address : @jackleet
For_More_Tools:
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.