SILENT KILLERPanel

Current Path: > > lib > udev


Operation   : Linux premium131.web-hosting.com 4.18.0-553.44.1.lve.el8.x86_64 #1 SMP Thu Mar 13 14:29:12 UTC 2025 x86_64
Software     : Apache
Server IP    : 162.0.232.56 | Your IP: 216.73.216.111
Domains      : 1034 Domain(s)
Permission   : [ 0755 ]

Files and Folders in: //lib/udev

NameTypeSizeLast ModifiedActions
hwdb.d Directory - -
rules.d Directory - -
ata_id File 41712 bytes April 22 2025 01:58:57.
cdrom_id File 33288 bytes April 22 2025 01:58:57.
collect File 21064 bytes April 22 2025 01:58:57.
fc_wwpn_id File 1125 bytes October 08 2022 11:49:23.
fido_id File 16824 bytes April 22 2025 01:58:57.
kdump-udev-throttler File 1444 bytes September 24 2024 08:36:00.
kpartx_id File 2383 bytes April 22 2025 01:55:39.
libinput-device-group File 16680 bytes June 29 2022 09:12:12.
libinput-fuzz-extract File 21160 bytes June 29 2022 09:12:12.
libinput-fuzz-to-zero File 12160 bytes June 29 2022 09:12:12.
mtd_probe File 12704 bytes April 22 2025 01:58:57.
prefixdevname File 1531272 bytes December 16 2019 19:52:38.
rename_device File 16856 bytes November 10 2022 08:01:00.
scsi_id File 54984 bytes April 22 2025 01:58:57.
v4l_id File 12280 bytes April 22 2025 01:58:57.

Reading File: //lib/udev/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

SILENT KILLER Tool