X7ROOT File Manager
Current Path:
/etc/sysconfig
etc
/
sysconfig
/
📁
..
📄
aibolit-resident
(30 B)
📄
aibolit-resident-hyperscan
(63 B)
📄
anaconda
(111 B)
📄
atd
(403 B)
📄
atop
(67 B)
📄
chronyd
(46 B)
📁
console
📄
cpupower
(150 B)
📄
crond
(110 B)
📄
dovecot
(72 B)
📄
ebtables-config
(417 B)
📄
exim
(142 B)
📄
exim.rpmorig
(21 B)
📄
firewalld
(73 B)
📄
garb
(560 B)
📄
grub
(361 B)
📄
htcacheclean
(350 B)
📄
httpd
(1.03 KB)
📁
imunify360
📄
ip6tables-config
(2.08 KB)
📄
iptables-config
(2.07 KB)
📄
irqbalance
(903 B)
📄
kdump
(2.44 KB)
📄
kernel
(185 B)
📄
lsapi-cache
(158 B)
📄
man-db
(310 B)
📄
modlsapi.secret
(16 B)
📁
modules
📄
named
(845 B)
📄
network
(99 B)
📁
network-scripts
📄
nftables.conf
(33.38 KB)
📄
nginx
(98 B)
📄
nginx-debug
(148 B)
📄
nrpe
(69 B)
📄
raid-check
(2.85 KB)
📄
rpcbind
(73 B)
📄
rsyslog
(196 B)
📄
run-parts
(0 B)
📄
samba
(428 B)
📄
selinux
(547 B)
📄
smartmontools
(186 B)
📄
snmpd
(103 B)
📄
snmptrapd
(108 B)
📄
sshd
(591 B)
📄
sshd-permitrootlogin
(161 B)
📄
sysstat
(1015 B)
📄
sysstat.ioconf
(6.28 KB)
Editing: 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=
Upload File
Create Folder