Linux ip-148-66-134-25.ip.secureserver.net 3.10.0-1160.119.1.el7.tuxcare.els10.x86_64 #1 SMP Fri Oct 11 21:40:41 UTC 2024 x86_64
Apache
: 148.66.134.25 | : 18.117.145.67
66 Domain
8.0.30
amvm
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
BLACK DEFEND!
README
+ Create Folder
+ Create File
/
usr /
lib /
udev /
[ HOME SHELL ]
Name
Size
Permission
Action
hwdb.d
[ DIR ]
drwxr-xr-x
rules.d
[ DIR ]
drwxr-xr-x
accelerometer
60.82
KB
-rwxr-xr-x
ata_id
48.06
KB
-rwxr-xr-x
cdrom_id
56.09
KB
-rwxr-xr-x
collect
31.54
KB
-rwxr-xr-x
kdump-udev-throttler
1.41
KB
-rwxr-xr-x
mtd_probe
10.9
KB
-rwxr-xr-x
phys-port-name-gen
1.18
KB
-rwxr-xr-x
rename_device
15.04
KB
-rwxr-xr-x
scsi_id
56.86
KB
-rwxr-xr-x
tascam_fpga
913
B
-rwxr-xr-x
tascam_fw
1.1
KB
-rwxr-xr-x
udev-kvm-check
15.12
KB
-rwxr-xr-x
v4l_id
23.3
KB
-rwxr-xr-x
Delete
Unzip
Zip
${this.title}
Close
Code Editor : kdump-udev-throttler
#!/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" exec 9>$throttle_lock if [ $? -ne 0 ]; then echo "Failed to create the lock file! Fallback to non-throttled kdump service restart" /bin/kdumpctl reload exit 1 fi flock -n 9 if [ $? -ne 0 ]; 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>&- /bin/kdumpctl reload exit 0
Close