On Fri, 9 May 2003, Hiddukel wrote: > Unfortunately I can't be much help with the freeze, but on a side note > about the sighandler code, when you use a sighandler it is very rare > that you will get a core file as the code handles the signal and does a > copyover in your case or exits normally after logging something in other > cases.
I get a core file every time it crashes. There's nothing inherent about a sighandler that says you can't have it drop a core file for you. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jennifer > King > Sent: Thursday, May 08, 2003 23:32 > To: [email protected] > Subject: Mud process dying a slow death... > > Time for a question dealing with my main port for once, and not the new > one. And this one is totally frying me. > > Rom2.4b4 with b6 patches, 5+ years worth of changes and rewrites.. I'm going to assume your problem is because of one of these "changes and rewrites". Because we don't know what these are, the best we can do is give you a random guess. > Now, here's the big problem. After the mud was restarted again, I was > watching the process in 'top'.. the cpu % would drop to 0.00% and the > mud > would just freeze up there. Usually whenever it would get stuck in a > loop, > the process cpu would skyrocket, but here it is down at nothing, and the > mud is totally frozen. And it does this for at least 2-3 hours > straight.. > every couple minutes. Sounds like there's a function somewhere blocking on something until it times out. My first guess would be some kind of networking function. Have you added anything that makes any sort of network connection that could be timing out on another host being down, or a DNS server being down, etc? Dennis
