Offline Recovery causing errors..
Posted: Tue Oct 07, 2003 5:09 pm
Here's the dealy..it's no longer like this, but this was what was happening..
I had been editing my mud from straight out of the BBS dats. However, when I did this, I would take the BBS down, edit, compile, and bring it back up. Sounds time consuming, but at this time I wasn't doing major edits, just item fixes, text block fixes, etc for the new races and classes. This wasn't too long ago, either..anyway. After I had finished editing and compiled an update, I would often time run a recovery (as suggested by many editors). When I brought the BBS back up, even after the database update was completed, the BBS lagged hard...kind of spastic though, because sometimes it would go to 1+ SECOND response time, sometimes down to like 20 ms, and it kinda just fluxuated thereabouts. Sometimes it would remain around 20 ms (which is still kinda bad, the BBS normally, and always did when this wasnt a factor, run at 6ms or less) so I would just leave it. The problem was, at cleanup the BBS would go down and not come back up. If, when the lag was bad from this situation, I would run a cleanup, the same thing. It gave me a total of 3 errors, only 2 of which I can name the file on...wgsmenu2.dat and wccacms2.dat. I would have to switch out the active monster dat, run another recovery, then bring the BBS up for it to work right.
The same thing happens when using a separate directory to edit, then switching the update over and running a cleanup. I would run a cleanup on the basis that regen was normally dead or would be soon by time I was ready for it, and a cleanup would have (or, should have) fixed both. However I got the same errors still. The only way it works right is if I edit to a separate directory, copy the update file over, then apply it through the MajorMUD sysop menu...
Just wondering if theres a reason? Or if anyone else has the same problem? I haven't had the problem in about a week or two, and that's how long it's been since I started to apply updates from the sysop menu as opposed to running a cleanup to institute my edits. I thought it was kind of weird, because before version 1.11n I didn't have this problem..
I had been editing my mud from straight out of the BBS dats. However, when I did this, I would take the BBS down, edit, compile, and bring it back up. Sounds time consuming, but at this time I wasn't doing major edits, just item fixes, text block fixes, etc for the new races and classes. This wasn't too long ago, either..anyway. After I had finished editing and compiled an update, I would often time run a recovery (as suggested by many editors). When I brought the BBS back up, even after the database update was completed, the BBS lagged hard...kind of spastic though, because sometimes it would go to 1+ SECOND response time, sometimes down to like 20 ms, and it kinda just fluxuated thereabouts. Sometimes it would remain around 20 ms (which is still kinda bad, the BBS normally, and always did when this wasnt a factor, run at 6ms or less) so I would just leave it. The problem was, at cleanup the BBS would go down and not come back up. If, when the lag was bad from this situation, I would run a cleanup, the same thing. It gave me a total of 3 errors, only 2 of which I can name the file on...wgsmenu2.dat and wccacms2.dat. I would have to switch out the active monster dat, run another recovery, then bring the BBS up for it to work right.
The same thing happens when using a separate directory to edit, then switching the update over and running a cleanup. I would run a cleanup on the basis that regen was normally dead or would be soon by time I was ready for it, and a cleanup would have (or, should have) fixed both. However I got the same errors still. The only way it works right is if I edit to a separate directory, copy the update file over, then apply it through the MajorMUD sysop menu...
Just wondering if theres a reason? Or if anyone else has the same problem? I haven't had the problem in about a week or two, and that's how long it's been since I started to apply updates from the sysop menu as opposed to running a cleanup to institute my edits. I thought it was kind of weird, because before version 1.11n I didn't have this problem..