Linux box325.rapidenet.ca 5.14.0-687.25.1.el9_8.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Jul 13 11:40:33 EDT 2026 x86_64
LiteSpeed
Server IP : 68.168.116.250 & Your IP : 216.73.216.215
Domains :
Cant Read [ /etc/named.conf ]
User : protectionrat
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
lib /
udev /
Delete
Unzip
Name
Size
Permission
Date
Action
hwdb.d
[ DIR ]
drwxr-xr-x
2026-06-26 05:25
rules.d
[ DIR ]
drwxr-xr-x
2026-07-31 05:25
ata_id
19.27
KB
-rwxr-xr-x
2026-06-25 00:28
cdrom_id
31.42
KB
-rwxr-xr-x
2026-06-25 00:28
dmi_memory_id
27.37
KB
-rwxr-xr-x
2026-06-25 00:28
fc_wwpn_id
1.11
KB
-rwxr-xr-x
2021-01-04 06:17
fido_id
23.27
KB
-rwxr-xr-x
2026-06-25 00:28
kdump-udev-throttler
1.63
KB
-rwxr-xr-x
2026-04-08 18:11
kpartx_id
2.33
KB
-rwxr-xr-x
2026-04-05 00:24
mtd_probe
15.23
KB
-rwxr-xr-x
2026-06-25 00:28
prefixdevname
1.45
MB
-rwxr-xr-x
2022-03-25 15:11
rename_device
15.17
KB
-rwxr-xr-x
2025-05-14 14:50
scsi_id
35.98
KB
-rwxr-xr-x
2026-06-25 00:28
v4l_id
15.23
KB
-rwxr-xr-x
2026-06-25 00:28
Save
Rename
#!/usr/bin/bash # This util helps to reduce the workload of kdump service restarting # on udev event. When hotplugging memory / CPU, multiple udev # events may be triggered concurrently, and obviously, we don't want # to restart kdump service for each event. # This script will be called by udev, and make sure kdump service is # restart after all events we are watching are settled. # On each call, this script will update try to aquire the $throttle_lock # The first instance acquired the file lock will keep waiting for events # to settle and then reload kdump. Other instances will just exit # In this way, we can make sure kdump service is restarted immediately # and for exactly once after udev events are settled. throttle_lock="/var/lock/kdump-udev-throttle" LUKS_CONFIGFS_REUSE=/sys/kernel/config/crash_dm_crypt_keys/reuse reuse_luks_keys() { [[ -f $LUKS_CONFIGFS_REUSE ]] || echo 1 > $LUKS_CONFIGFS_REUSE } unuse_luks_keys() { [[ -f $LUKS_CONFIGFS_REUSE ]] || echo 0 > $LUKS_CONFIGFS_REUSE } if ! exec 9> $throttle_lock; then echo "Failed to create the lock file! Fallback to non-throttled kdump service restart" /bin/kdumpctl reload exit 1 fi if ! flock -n 9; then echo "Throttling kdump restart for concurrent udev event" exit 0 fi # Wait for at least 1 second, at most 4 seconds for udev to settle # Idealy we will have a less than 1 second lag between udev events settle # and kdump reload sleep 1 && udevadm settle --timeout 3 # Release the lock, /bin/kdumpctl will block and make the process # holding two locks at the same time and we might miss some events exec 9>&- reuse_luks_keys /bin/kdumpctl reload unuse_luks_keys exit 0