Re: Newbie Alert #2: Keeping the MOO going

• Date: Fri, 19 Jan 1996 15:59:55 PST
• From:
  Sander van Drooge <sander@dds.nl>
• cc: moo-cows@parc.xerox.com, cindy@fred.net
• Content-Type: TEXT/PLAIN; charset=US-ASCII
• In-Reply-To: <199601192338.SAA05477@bronze.interlog.com>

On Fri, 19 Jan 1996 ksc@interlog.com wrote:

> Hello,
> 
> Things are going well. I'm now running the Oct94 LambdaMOO db, and
> am finding it pretty easy to set up. But, there's one more thing:
> 
> To start the moo, I log in to my Linux pc and run the moo executable.
> (moo Lambda.db dumplambda.db),
> and it goes on its merry way, but is running in the foreground (it
> lists what it's doing as people connect and disconnect, etc.) So,
> if I log off, the process is killed. How do I keep the MOO running
> without the security risk of leaving myself logged on?

You can start the moo (just like other Unix processes) in the background, by
starting the moo with 

moo <startup-db> <dump-db> <portnumber> &'

If you want to keep the log messages, use: 

moo <startup-db> <dump-db> <port> >> moo.log &

> Also, if it crashes, how do I restart it without losing all my work?
> Do I just use the previous dumplambda db as the startup db?

You should use the most recent dump of your moo, which you can use as the
startup-database.
 
Regards,

Sander

• Re: Newbie Alert #2: Keeping the MOO going
• From: Mike Thompson <shadowr@nando.net>

• Newbie Alert #2: Keeping the MOO going
• From: ksc@interlog.com (Kim Silk-Copeland by way of ksc@interlog.com (Kim Silk-Copeland))

• Prev: Newbie Alert #2: Keeping the MOO going
• Next: Re: Newbie Alert #2: Keeping the MOO going
• Index: MOO-cows
• Thread: MOO-cows