On Mon, 4 Feb 2002, Tom Whiting wrote: it's not writing to a file, it's writing to a descriptor. somehow, you're either preserving dead connections across hotboots or generating false ones. check over comm.c to make sure you didn't change any of the timeout, quit, or login logic.
good luck, > Greetings, list > A rather intriguing situation has come up just the past few days and I > can't for the life of me figure out why. > Every once in a while, on random, when I run a copyover, it's not > restored from correctly at all.. Instead, I get spammed with this in > whatever log file: > Write_to_descriptor: Bad file descriptor > Write_to_descriptor: Bad file descriptor > Write_to_descriptor: Bad file descriptor > Write_to_descriptor: Bad file descriptor > Write_to_descriptor: Bad file descriptor > Write_to_descriptor: Bad file descriptor > Now, from what I can tell, none of the files were changed that are > necessary for startup. Even killing the mud process, and letting it > restart on its own seems to work.. Yet, those log files add up. When I > first noticed this, in < 2 minutes, I had 20+m of log additions. > I'm not exactly sure what could be causing this at the moment, any > thoughts, ideas where to check?? > > ------------------------------------------- > TJW: Head tech, Dreamless Realms Mud > Personal: http://twhiting.kyndig.com > Mud: http://drealms.kyndig.com > Snippets http://drealms.kyndig.com/snippets > Telnet telnet://drealms.kyndig.com:9275 > The OLC2 Pages http://olc.kyndig.com > ------------------------------------------- > > > > > > -- -- Blue Lang http://www.b-side.org/~blue editor, b-side.org http://www.b-side.org bug generation unit, alanthia mud alanthia.org 1536 integration engineer, veritas software http://www.veritas.com
