Linux bear.hostingplus.cl 4.18.0-553.111.1.lve.el8.x86_64 #1 SMP Fri Mar 13 13:42:17 UTC 2026 x86_64
LiteSpeed
Server IP : 192.140.57.17 & Your IP : 216.73.216.124
Domains :
Cant Read [ /etc/named.conf ]
User : explo
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-05-02 01:52
rules.d
[ DIR ]
drwxr-xr-x
2026-05-02 01:52
ata_id
40.73
KB
-rwxr-xr-x
2026-04-23 07:13
cdrom_id
32.51
KB
-rwxr-xr-x
2026-04-23 07:13
collect
20.57
KB
-rwxr-xr-x
2026-04-23 07:13
fc_wwpn_id
1.1
KB
-rwxr-xr-x
2022-10-08 08:49
fido_id
16.43
KB
-rwxr-xr-x
2026-04-23 07:13
kdump-udev-throttler
1.41
KB
-rwxr-xr-x
2026-02-10 14:24
kpartx_id
2.33
KB
-rwxr-xr-x
2026-04-14 18:56
mtd_probe
12.41
KB
-rwxr-xr-x
2026-04-23 07:13
prefixdevname
1.46
MB
-rwxr-xr-x
2019-12-16 16:52
rename_device
16.48
KB
-rwxr-xr-x
2025-11-10 07:42
scsi_id
53.71
KB
-rwxr-xr-x
2026-04-23 07:13
v4l_id
12
KB
-rwxr-xr-x
2026-04-23 07:13
Save
Rename
#!/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