> > jmlemke@icaen.uiowa.edu wrote: > > > > Ok, I seem to have narrowed this down a little.. What seems to be > > happening is that whenever my mud recieves a Segmentation Fault, it closes > > without resetting the port... I got this far after toying with things a > > while and duplicating the error a few times... So now several of said ports > > are gone... I consider myself a decent coder, but sockets and stuff are a > > little over my head.. From what it looks like, I need either a) a way to > > close that socket/port when the mud gets a seg fault, or b) write some kind > > of process to run between autoruns that will attatch itself to that > > socket/port and close it if it is left open. Anyone know if either of > > these are possible, or maybe even could point me in the direction of > > trying to figure this out? > > > > TIA... > > --Pegasus of OnyxMUD > > > have you tried doing that 'ps -ux' then do 'kill <pid#>' where pid# is > the pid# that is set to your mud > My problem is that there are NO mud processes running. There are no processes at all running that would hog the port but the port isn't getting reset or something like that. Like I said I don't know how sockets work but was hoping someone would... So if someone could help figure this little problem out.. It would be very much appreciated.. --Pegaus of OnyxMUD +-----------------------------------------------------------+ | Ensure that you have read the CircleMUD Mailing List FAQ: | | http://cspo.queensu.ca/~fletcher/Circle/list_faq.html | +-----------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/18/00 PST