Subject: Replacing the .db

From: Allan Alford <[email-masked]>
Date: Thu, 7 Oct 1993 17:51:55 -0700

We are running Solaris, and have our MOO set on a port.
For reasons I don't care to go into :) we need
to replace the existing .db.

I ftp'd the newest version from the site, deleted ALL the old .db's,
including the .log, .old, and .new files.

for some reason, even after doing "restart" with the new .db's name
(same port), the system recreates the old .db name (with a .new
extension, I believe), and when I go in, it's still all the same.

Does "moo" encapsulate and contain the .db, or reference it somehow?

I tried using "moo" by hand with the input-db as the new release
of the .db and the dump-db as the new .db file name I wanted...
The system loaded the new stuff, but then just waited and waited
and waited and waited...

I'm o.k. with MOO, but I'm lousy with UNIX! 

Thoroughly confused, and desparate to get this fixed,
Chiphead

---

From: [email-masked] (Tim Sailer)
Date: Fri, 8 Oct 1993 05:39:09 -0700

> Thoroughly confused, and desparate to get this fixed,

Look in 'restart'. Its a script file. Thats where the db name is
hardcoded.

Tim

-- 
                            Tim Sailer
                      [email-masked]
             "The one who dies with the most toys, wins!"