I've never hit a down side to doing this. I am untrained in debugging an ANSYS crash from reading a core dump file, so its value to me is zero. (In my understanding, the core file is a copy of what's in the machine's memory at the time of the crash). Perhaps, someone at ANSYS or your hardware vendor can interpret such a file, but as a regular user (I suspect that includes most of us), I just delete the core file and start ANSYS again after a crash, and try it again !
If you have reservations, hold off a few days to see if any of the experts shoot down my advice.
Dave Johnson Penn State-Erie Erie, PA, USA
Tom.Davis@f... wrote:
> From: Tom.Davis@f...
> Dave,
> This sounds like a good thing to do. However, before I implement it, can > you tell me what the downside is?
> Thanks.
> TWD
> Thomas W. Davis, P. E. > FSI International (http://www.fsi-intl.com/) > 322 Lake Hazeltine Drive > Mail Station 4-1035 > Chaska, Minnesota 55318 > PHONE 612-361-7359, FAX 612-361-7393 > tom.davis@f...
> From: Dave & Kathleen Johnson
> For years, I have used the line:
> limit coredumpsize 0
> in my .cshrc file on Unix machines. (This resrticts the size of a > 'core' file to 0 bytes and allows a crash finish quickly)
> Dave Johnson > Penn State - Erie > Erie, PA, USA