Linux business72.web-hosting.com 4.18.0-553.lve.el8.x86_64 #1 SMP Mon May 27 15:27:34 UTC 2024 x86_64
LiteSpeed
: 162.0.229.97 | : 13.58.72.59
Cant Read [ /etc/named.conf ]
8.1.30
temmmp
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
README
+ Create Folder
+ Create File
/
usr /
lib /
node_modules /
npm /
node_modules /
signal-exit /
[ HOME SHELL ]
Name
Size
Permission
Action
CHANGELOG.md
1.05
KB
-rw-r--r--
LICENSE.txt
748
B
-rw-r--r--
README.md
1.46
KB
-rw-r--r--
index.js
3.82
KB
-rw-r--r--
package.json
1.78
KB
-rw-r--r--
signals.js
1.26
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : README.md
# signal-exit [](https://travis-ci.org/tapjs/signal-exit) [](https://coveralls.io/r/tapjs/signal-exit?branch=master) [](https://www.npmjs.com/package/signal-exit) [](https://ci.appveyor.com/project/bcoe/signal-exit) [](https://github.com/conventional-changelog/standard-version) When you want to fire an event no matter how a process exits: * reaching the end of execution. * explicitly having `process.exit(code)` called. * having `process.kill(pid, sig)` called. * receiving a fatal signal from outside the process Use `signal-exit`. ```js var onExit = require('signal-exit') onExit(function (code, signal) { console.log('process exited!') }) ``` ## API `var remove = onExit(function (code, signal) {}, options)` The return value of the function is a function that will remove the handler. Note that the function *only* fires for signals if the signal would cause the proces to exit. That is, there are no other listeners, and it is a fatal signal. ## Options * `alwaysLast`: Run this handler after any other signal or exit handlers. This causes `process.emit` to be monkeypatched.
Close
