I don't know what sig handler you've added.. but if you don't do anything to stop the process in your handler, it'll go back to the point in the code where the signal was raised and try to continue.. which most likely means it'll crash again. and again... Personally, when I catch a signal, after saving some debugging info and forking a fresh copy of the mud, I signal(sig, SIG_DFL) then raise(sig), so it goes ahead and dies, dumping a core. Then again if you have hd constraints, you may not want it dumping a core at all. --Palrich.
> It seems i am having problems with a sig_handler code > i had added to my code. The last_command.txt will save > massive logs of the same command. Is there an easy way > to fix this so it will only save one time and not take > up all the space?
