Honsetly, I don't. I log A LOT.
I log every command types, every mob prog, obj prog, room prog executed. All using that methodology. Now, I also log user sessions. Like from log in to log out. I have quite a few gig of player log files. With this, I've created an fp in pcdata and write to it during the user session. This has been instrumental in troubleshooting bugs. As for the other logs... Open, write, close. The only other option, I can think of, is open all the files when the mud starts, and pass *fp instead of the filename to appropriate functions. And instead of closing the file, flush it. > -----Original Message----- > From: Chris "Winston" Litchfield [mailto:[EMAIL PROTECTED] > Sent: Saturday, October 04, 2003 12:20 AM > To: [email protected] > Subject: Log performance. > > Greetings, > > I have a question/request for ideas. Basically the problem I > have is this. > After a long time (5+ years) of direct development on my mud, > it is filled with GREAT log lines. Thats not really the > problem but I believe that I have so many now that the > constant writing to disk > > Every logfile entry does an open file, write line, close file. > > This is a huge performance overhead. I like to know things > that happen upon a crash.. but still.. > > So the question is: Anyone do logging differently that may > be much better performance? (ie: not so many constant > writes, but still maintain the same information). > > Chris "Winston" Litchfield. > > > > -- > ROM mailing list > [email protected] > http://www.rom.org/cgi-bin/mailman/listinfo/rom >
