Gecko [ naturenectar.co.uk ]

Linux srv25.usacloudserver.us 5.14.0-570.39.1.el9_6.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Sep 4 05:08:52 EDT 2025 x86_64
LiteSpeed
Server IP : 23.137.84.82 & Your IP : 216.73.216.127
Domains : Cant Read [ /etc/named.conf ]
User : epicgamerzoneco

Name	Size	Permission	Date
hwdb.d	[ DIR ]	drwxr-xr-x	2025-08-15 18:20
rules.d	[ DIR ]	drwxr-xr-x	2025-08-15 18:39
ata_id	19.27 KB	-rwxr-xr-x	2025-06-24 13:02
cdrom_id	31.42 KB	-rwxr-xr-x	2025-06-24 13:02
dmi_memory_id	27.36 KB	-rwxr-xr-x	2025-06-24 13:02
fc_wwpn_id	1.11 KB	-rwxr-xr-x	2021-01-04 06:17
fido_id	23.27 KB	-rwxr-xr-x	2025-06-24 13:02
kdump-udev-throttler	1.41 KB	-rwxr-xr-x	2025-08-15 07:54
kpartx_id	2.33 KB	-rwxr-xr-x	2025-06-24 13:12
mtd_probe	15.23 KB	-rwxr-xr-x	2025-06-24 13:02
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.95 KB	-rwxr-xr-x	2025-06-24 13:02
v4l_id	15.23 KB	-rwxr-xr-x	2025-06-24 13:02

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"

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