Linux thaedus.aserv.co.za 5.14.0-687.24.1.el9_8.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Jul 9 18:14:06 EDT 2026 x86_64
LiteSpeed
Server IP : 197.242.159.149 & Your IP : 216.73.217.62
Domains :
Cant Read [ /etc/named.conf ]
User : bigpuxtb
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
etc /
sysconfig /
Delete
Unzip
Name
Size
Permission
Date
Action
console
[ DIR ]
drwxr-xr-x
2025-03-12 19:47
imunify360
[ DIR ]
drwxr-xr-x
2026-07-26 23:47
kcare
[ DIR ]
drwxr-xr-x
2026-08-05 07:47
modules
[ DIR ]
drwxr-xr-x
2025-03-12 19:47
network-scripts
[ DIR ]
drwxr-xr-x
2026-07-12 09:59
aibolit-resident
30
B
-rw-r-----
2026-07-22 08:27
aibolit-resident-hyperscan
63
B
-rw-r--r--
2026-08-05 08:40
anaconda
112
B
-rw-r--r--
2026-07-11 11:16
atd
403
B
-rw-r--r--
2025-11-12 00:38
autofs
339
B
-rw-r--r--
2025-09-21 12:22
certmonger
9
B
-rw-r--r--
2025-01-15 09:52
chronyd
50
B
-rw-r--r--
2026-04-09 00:49
cpupower
150
B
-rw-r--r--
2026-08-01 10:15
crond
110
B
-rw-r--r--
2026-04-09 05:59
dovecot
72
B
-rw-------
2026-07-13 00:00
exim
142
B
-rw-r--r--
2026-07-12 10:20
exim.rpmorig
142
B
-rw-r--r--
2026-07-12 10:18
garb
560
B
-rw-r--r--
2026-05-22 03:36
htcacheclean
350
B
-rw-r--r--
2026-06-10 15:51
httpd
1.03
KB
-rw-r--r--
2026-06-10 15:51
ip6tables
635
B
-rw-------
2025-02-13 03:59
ip6tables-config
2.08
KB
-rw-------
2025-02-13 03:59
iptables
8.85
KB
-rw-------
2026-07-13 03:01
iptables-config
2.07
KB
-rw-------
2025-02-13 03:59
iptables.rpmnew
550
B
-rw-------
2025-02-13 03:59
iptables.save
8.85
KB
-rw-------
2026-07-13 03:01
irqbalance
1.37
KB
-rw-r--r--
2026-04-08 16:39
kdump
2.66
KB
-rw-r--r--
2026-04-08 18:11
kernel
185
B
-rw-r--r--
2026-07-12 09:59
man-db
310
B
-rw-r--r--
2025-09-21 12:04
named
845
B
-rw-r--r--
2026-06-10 13:21
network
74
B
-rw-r--r--
2026-07-12 13:46
nftables.conf
364
B
-rw-------
2026-06-03 10:49
raid-check
2.85
KB
-rw-r--r--
2026-06-23 11:55
rpcbind
73
B
-rw-r--r--
2024-04-03 13:53
rsyslog
196
B
-rw-r--r--
2026-04-14 15:35
run-parts
0
B
-rw-r--r--
2022-04-11 19:54
samba
428
B
-rw-r--r--
2026-06-10 13:28
saslauthd
429
B
-rw-r--r--
2026-06-09 19:08
selinux
17
B
-rw-r--r--
2026-07-12 13:46
smartmontools
201
B
-rw-r--r--
2026-04-08 19:05
snmpd
103
B
-rw-r--r--
2026-04-10 02:30
snmptrapd
108
B
-rw-r--r--
2026-04-10 02:30
sshd
384
B
-rw-r-----
2026-07-29 23:09
svnserve
138
B
-rw-r--r--
2025-09-22 11:49
sysstat
1.63
KB
-rw-r--r--
2026-04-15 10:16
sysstat.ioconf
6.31
KB
-rw-r--r--
2021-06-07 12:21
Save
Rename
#!/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=