Unnamed repository
86b251765e
In RHEL6, vmcore file was created if panic occurred during shutdown. This was very useful for analyzing problems during the shutdown sequence. However, in RHEL7, vmcore will not be created after kdump service is stopped. This will make it very difficult to solve problems during shutodwn. The reason why kdump fails to dump vmcore is kdump is stopped too early during the power is off. If add "DefaultDependencies=no" to the [Unit] of kdump.service , kdump will not be stopped by systemd after shutdown command. The manpage of systemd.unit about the DefaultDependencies: If true, (the default), a few default dependencies will implicitly be created for the unit. The actual dependencies created depend on the unit type. For example, for service units, these dependencies ensure that the service is started only after basic system initialization is completed and is properly terminated on system shutdown. The manpage about basic.target: A special target unit covering basic boot-up. systemd automatically adds dependencies of the types Requires= and After= for this target unit to all services (except for those with DefaultDependencies=no). Usually this should pull-in all mount points, swap devices, sockets, timers, and path units and other basic initialization necessary for general purpose daemons. So "DefaultDependencies=no" can keep kdump not stopped too early. But to make it start when power on, add After=basic.target will be better. The systemd-devel mailed to me: using DefaultDependencies=no but also After=basic.target will make sure the service isn't started too early (but kept until systemd's final process killing spree). Signed-off-by: Chao Fan <cfan@redhat.com> Acked-by: Minfei Huang <mhuang@redhat.com> |
||
|---|---|---|
| anaconda-addon | ||
| .gitignore | ||
| 98-kexec.rules | ||
| dracut-kdump-capture.service | ||
| dracut-kdump-emergency.service | ||
| dracut-kdump-error-handler.service | ||
| dracut-kdump-error-handler.sh | ||
| dracut-kdump.sh | ||
| dracut-module-setup.sh | ||
| dracut-monitor_dd_progress | ||
| fadump-howto.txt | ||
| kdump-dep-generator.sh | ||
| kdump-in-cluster-environment.txt | ||
| kdump-lib-initramfs.sh | ||
| kdump-lib.sh | ||
| kdump.conf | ||
| kdump.conf.5 | ||
| kdump.service | ||
| kdump.sysconfig | ||
| kdump.sysconfig.i386 | ||
| kdump.sysconfig.ppc64 | ||
| kdump.sysconfig.ppc64le | ||
| kdump.sysconfig.s390x | ||
| kdump.sysconfig.x86_64 | ||
| kdumpctl | ||
| kexec-kdump-howto.txt | ||
| kexec-tools-2.0.3-disable-kexec-test.patch | ||
| kexec-tools-2.0.7-kexec-ppc64-disabling-exception-handling-when-buildi.patch | ||
| kexec-tools-2.0.7-kexec-ppc64-move-to-device-tree-version-17.patch | ||
| kexec-tools-2.0.7-ppc64-kdump-Fix-ELF-header-endianess.patch | ||
| kexec-tools-2.0.7-Provide-an-option-to-use-new-kexec-system-call.patch | ||
| kexec-tools.spec | ||
| mkdumprd | ||
| mkdumprd.8 | ||
| README | ||
| rhcrashkernel-param | ||
| sources | ||
| zanata-notes.txt | ||
Adding a patch to kexec-tools ============================= There is a mailing list kexec@lists.fedoraproject.org where all the dicussion related to fedora kexec-tools happen. All the patches are posted there for inclusion and committed to kexec-tools after review. So if you want your patches to be included in fedora kexec-tools package, post these to kexec@lists.fedoraproject.org. One can subscribe to list and browse through archives here. https://admin.fedoraproject.org/mailman/listinfo/kexec