> try this: > in the shell type ulimit -c > Chances are you'll find it's set to 0 if it's a later system > to fix this: > open up ~/.bash_profile (if you're using bash) > type ulimit -c unlimited > relog > This will tell ulimit NOT to limit your core usage .
Actually, a better way would be to check out the man files on getrlimit and setrlimit. That way you can set the core size on each execution of your mud, and if you move servers, you wont have that issue again. Setting your ulimit to unlimited on a server is a very good way to overblow your quota if your still in a "debugging phase" (though, if your still in that phase, I'd just recommend setting something up on your home system to do all of that work, and only commiting to the primary server once a stable build can be achieved.). Also, on some systems, they will not allow you to modify your .bash_profile, or for that matter, any of your .XXXX_profile or .XXXXrc files. So as mentioned at the beginning, it's prolly just better in the long run to use methods like getrlimit and setrlimit. Best of luck.
