Why does /etc/init.d/kdump call cp instead of /sbin/makedumpfile?

Solution Unverified - Updated -

Issue

  • /etc/init.d/kdump should call /sbin/makedumpfile instead of cp.
  • The kdump init script uses "cp --sparse=always /proc/vmcore $coredir/vmcore-incomplete" to save the crashed kernel's memory image instead of /sbin/makedumpfile.

Environment

  • Red Hat Enterprise Linux 5
  • kexec-tools-1.101-125.el5

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.