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

[Nick Burtner]

(Forgot to actually post this to the list)

>From the looks of it, there's a corrupted object in there.  Do you know the
max dbref of your game?  If this is a bad one, its not a hard task to modify
the DB by hand (well, it wasn't a few years ago.  I've been out of the Penn
loop for a little while) and remove the offending object.  After that, it
should startup fine.

Of course, I should state that this is for more advanced users.  I don't
know your skill level in these things, so I don't know if you're comfortable
with that or not.

On Thu, Jul 24, 2008 at 7:39 AM, Jeff Ferrell <jmferrell at mac.com> wrote:

> 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.
>
> _______________________________________________
> PennMUSH mailing list
> PennMUSH at pennmush.org
> http://www.pennmush.org/mailman/listinfo/pennmush
> PennMUSH FAQ-o-matic! http://www.pennmush.org/cgi-penn/fom
>