I could tell it was doing something like that, looping auto_shutdown, etc, unfortunately I couldn't figure out how to get it to stop. Like I said, I'm clueless when it comes to signals. After going through man signal, the best thing I can find is SIG_IGN. Where would I need to put sig_ign though? In comm (where init_signal is at), or act_wiz2 (where auto_shutdown's at). And how would I go about using it?? Just call SIG_IGN?? Like I said I've got no clue when I'm dealing with signals whatsoever. Sorry to be such a bother. ------------------------------------------- TJW: Head tech, Dreamless Realms Mud Web: http://drealms.kyndig.com Snippets http://drealms.kyndig.com/snippets Telnet telnet://drealms.kyndig.com:9275 The OLC2 Pages http://olc.kyndig.com -------------------------------------------
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Reus Sent: Monday, January 07, 2002 5:20 PM To: [email protected] Subject: Re: boggled You have to tell redhat to ignore the signal the second time..otherwise it repeatly trys to autoshutdown the mud. man signal how to do it, because off the top of my head it escapes me.. Zartha who had this problem. ----- Original Message ----- From: "Tom Whiting" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Monday, January 07, 2002 4:14 PM Subject: boggled > > Here's an odd little error I continually get when the mud crashes, > corrupting the core files and all. From what I can see, it doesn't have > anything to do with rom @ all, but I might be misinterpreting something > here. Here's the output from gdb: > > #1151 0x806a5f9 in do_auto_shutdown () at act_wiz2.c:1868 > #1152 0x807bcb3 in sig_handler (sig=-1074789136) at comm.c:614 > #1153 0x40066c48 in __restore () at > ../sysdeps/unix/sysv/linux/i386/sigaction.c:127 > > -- ROM mailing list [email protected] http://www.rom.org/cgi-bin/mailman/listinfo/rom
