On Fri, Dec 03, 2010 at 05:14:00PM +0100, Louis Bouchard wrote: > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> > <html> > <head> > > <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> > </head> > <body text="#000000" bgcolor="#ffffff"> > Hello (again)<br> > <br> > I did not think that I would come back to you so quickly, but I am > having an issue with RHEL6 implementation of kexec-tools (apparently > adapted for kexec-tools 2.0) while testing crashdc on RHEL6 (the > initial release).<br> > <br> > Everytime I trigger a crash with 'kdump_post' set to > /var/crash/scripts/kdump_post.sh I get the following from busybox : > kdump-post.sh: applet not found<br> > <br> > <blockquote><tt>Copying data : [100%]</tt><br> > <tt>Saving core complete</tt><br> > <tt>kdump-post.sh: applet not found</tt><br> > <tt>dropping to initramfs shell</tt><br> > <tt>exiting this shell will reboot your system</tt><br> > </blockquote> > For a while, I thought that my crashdc calling script was in cause, but > I changed kdump_post.sh to one single "echo This is working" line and I > still get the same thing :<br> > <br> > <blockquote><tt># cat /var/crash/scripts/kdump-post.sh</tt><br> > <tt>echo "This is working"</tt><br> > <tt>/var/crash/scripts/kdump-post.sh</tt><br> > <tt>kdump-post.sh: applet not found</tt><br> > <tt>msh/ # /var/crash/scripts/kdump-post.sh</tt><br> > <tt>This is working</tt><br> > </blockquote> I'm kind of suprised this is working at all. I don't see a #!/bin/sh or #!/bin/msh line at the top of the script. How does the system know what interpreter to use? Neil
