--- Tony Kuiper <[EMAIL PROTECTED]> wrote: > Try waiting until the mud is locked, then attach to the process with > gdb. This will allow you to see where it's "locking" and diagnose the > problem from there. :-) > > Tony
The probram isn't locked.. It's being killed. > ----- Original Message ----- > From: "Adrian Allen" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Monday, December 16, 2002 4:15 AM > Subject: SIGKILL > > > > Sometimes within less than a minute of booting the mud it will just > > stop running. I had no idea why until tonight I was using gdb to > > debug an area file and after I had the bugs worked out it happened > > I remember seeing this one other time using gdb and I know its not > > caused by the bug in my area file, having a door reset to a null exit > > and then fixing it wouldnt cause this. Its something else. Any ideas? > > > > > > Program terminated with signal SIGKILL, Killed. The only people on a *nix system who can send a kill signal to your program is you, or the admin. So unless you have some automated script that is killing it, I'd say to consult with your admin and find out why your program is being killed. ~Kender ===== -----BEGIN GEEK CODE BLOCK----- Version 3.1 GCS/L/C/O d-(+) s++: a-- C+++$>++++ UBLS++++$ P+++(--)$ L+++>++++ E--- W+>++$ N !o K? w(--) !O M- !V PS+ PE(++) Y+ PGP->+ t+ 5 X+() R(+) tv+@ b++(+++) !DI+++ D G(-) e>+++$ h---() r+++ y+++ ------END GEEK CODE BLOCK------ __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
