Description of problem: The mkdumprd command creates an init script that doesn't work if the remote user that is being used to receive the dump is configured with a restricted shell (rksh) for one simple reason: Restricted shell forbids the use of redirection. Version-Release number of selected component (if applicable): Applicable for all versions of versions of kexec-tools shipped with RHEL How reproducible: Configure kdump to dump vmcore via ssh, with the remote kdump user configured to use a restricted shell (rksh), and trigger a kernel panic Actual results: Dumping will fail since restricted shell forbids the use of redirection. Expected results: Dumping should work even if the remote user is configured with a restricted shell (rksh)
Created attachment 568738 [details] Patch to allow network dumps when the remote use is in a restricted shell This patch changes the mkdumprd command to use the tee command rather than classic redirection when cat'ing the dump to a file via SSH. It was tested with kexec-tools-1.102pre-126.el5_6.6.x86_64.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.
Created attachment 597202 [details] use dd instead of cat in ssh vmcore saving Hi, Same reason with rhel6 bug 801497, tee will create lots of output to stdout, so we will use "dd of=". Backport the patch from rhel6
Hi, Subin I uploaded rhel5 srpm and rpms to below url http://people.redhat.com/ruyang/aa60a46e66f4725af97709df3eb60158/ Could you ask customer to test? Thanks.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0012.html