Linux server.thearyasamaj.org 4.18.0-553.56.1.el8_10.x86_64 #1 SMP Tue Jun 10 05:00:59 EDT 2025 x86_64
Apache
: 103.90.241.146 | : 216.73.216.222
Cant Read [ /etc/named.conf ]
5.6.40
ftpuser@mantra.thearyasamaj.org
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
CREATE WP USER
README
+ Create Folder
+ Create File
/
usr /
share /
doc /
kexec-tools /
[ HOME SHELL ]
Name
Size
Permission
Action
News
2.74
KB
-rw-r--r--
TODO
528
B
-rw-r--r--
early-kdump-howto.txt
3.52
KB
-rw-r--r--
fadump-howto.txt
15.03
KB
-rw-r--r--
kdump-in-cluster-environment.t...
3.74
KB
-rw-r--r--
kexec-kdump-howto.txt
42.33
KB
-rw-r--r--
live-image-kdump-howto.txt
765
B
-rw-r--r--
supported-kdump-targets.txt
4.1
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : live-image-kdump-howto.txt
Kdump now works on live images with some manual configurations. Here is the step by step guide. 1. Enable crashkernel reservation Since there isn't any config file that can be used to configure kernel parameters for live images before booting them, we have to append 'crashkernel' argument in boot menu every time we boot a live image. 2. Change dump target in /etc/kdump.conf When kdump kernel boots in a live environment, the default target /var/crash is in RAM so you need to change the dump target to an external disk or a network dump target. Besides, make sure that "default dump_to_rootfs" is not specified. 3. Start kdump service $ kdumpctl start 4. Trigger a kdump test $ echo 1 > /proc/sys/kernel/sysrq $ echo c > /proc/sysrq-trigger
Close