Yeah, the log file is huge (over 6 MB), but I'm not quota'd (my mud is the only thing running on the server really), and after I restarted the mud, it opened the same log file and continued to write to it for the rest of the day without incident. I haven't made any changes that have to do with reading or writing files lately.. When I tried to connect to the shell afterwards to see what happened, I couldn't reach the machine at all for a few minutes, which made me wonder if it was an OS and/or networking problem that caused player descriptors to start blocking when they shouldn't have.
> > That is repeated literally over 10,000 times in my log file... > > Then the process died. I'm not sure how it died, there was no core file > > and it didn't find any exit()s. > > --Palrich. > go into logs, and du -sm (insertlatestlog.log here) > chances are it's rather intense and large. > I'd bet that the game's shuttin down because of the disk usage.. if you've got > that up 10k times in your log file, that will take up quite a bit of space, > and if you're quota'd you're more than likely exceeding that quota just in > logs. > > as to the problems, what did you change? That's the first place to start > lookin. It's possible that you didn't close an fp, or you have an fp open, or > opened too early.
