[PennMUSH] Blasting my MUSH back to the stone age?

[Jeff Ferrell]

Hi, again!

Please disregard everything from the previous exchange. I did  
something *very, VERY* stupid and catastrophic to my system, that is  
far too embarrassing to admit, and totally screwed up the startup  
execution. (Ok, I'll admit it, for anyone puzzling over the log in my  
last message: In a fit of total ignorance, I had *replaced* /bin/sh  
WITH my python script. How's that for stupid, huh?) This morning I  
woke up, and had the answer. So that's fixed -- the MUSH starts to  
start up properly.

I've got a different problem, though... I've got a database from a  
couple of months back, at least, but it was kicking out some small  
errors on startup; just some little glitches. I've gone in and cleaned  
all those out, I think, and now my log is showing this:

ERROR: No end of dump after object #7961

The database file is showing !7963 and then ***END OF DUMP***

I'm assuming the database "knows" when it should expect an end? Is  
there a way I can doctor it to include the last two objects in the  
count, or is there something more serious going on here?

Thanks for all your input so far!
Jeff.