<p>I've inherited someone else's monster of a BASH script.  The script was written in such a way that it uses a ridiculous amount of memory (around 1GB).  I can run it from a shell with out issue, but if I run it from cron I crashes with a sig fault.  </p>

<p>Apart from digging into the poorly commented behemoth, is there a way to run it from cron with out running into the sig fault?  </p>

<p>Cheers,</p>

<p>Steve</p>

When you run something using cron you'll encounter issues with the environment variables being different or simply not set as compared to your own variables when you manually execute. Often things like the PATH aren't set properly when cron executes something, so it's important to supply full paths to executables within the script, even for things such as perl or common commands that you thing
should
be found in the default PATH. Without more info it's hard to speculate on what precisely the problem is.