Linux ip-172-31-23-120.eu-west-1.compute.internal 5.10.245-245.983.amzn2.x86_64 #1 SMP Wed Dec 3 00:02:10 UTC 2025 x86_64
Apache/2.4.65 () OpenSSL/1.0.2k-fips
: 172.31.23.120 | : 64.252.114.248
Cant Read [ /etc/named.conf ]
8.2.29
apache
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
/
etc /
cron.daily /
[ HOME SHELL ]
Name
Size
Permission
Action
logrotate
219
B
-rwx------
man-db.cron
618
B
-rwxr-xr-x
mlocate
208
B
-rwx------
Delete
Unzip
Zip
${this.title}
Close
Code Editor : man-db.cron
#!/bin/bash if [ -e /etc/sysconfig/man-db ]; then . /etc/sysconfig/man-db fi if [ "$CRON" = "no" ]; then exit 0 fi renice +19 -p $$ >/dev/null 2>&1 ionice -c3 -p $$ >/dev/null 2>&1 LOCKFILE=/var/lock/man-db.lock # the lockfile is not meant to be perfect, it's just in case the # two man-db cron scripts get run close to each other to keep # them from stepping on each other's toes. The worst that will # happen is that they will temporarily corrupt the database [[ -f $LOCKFILE ]] && exit 0 trap "{ rm -f $LOCKFILE ; exit 0; }" EXIT touch $LOCKFILE # create/update the mandb database mandb $OPTS exit 0
Close
