You should use the ./restart script, even if the MUCK isn't already running. See
what happens then.
-----Original Message-----
From: Pete Strover <doklands@...>

Date: Wed, 17 Dec 2008 15:45:45
To: <protomuck@yahoogroups.com>
Subject: Re: [protomuck] Trouble compiling on Debian


Kelketek Rritaa wrote:
> Create a muck.conf file in the same directory as restart with contents similar
to these (this is what's in mine)
>
>
> MUCKDB="proto.db"
> MUCKOUT="proto.out"
> MAINPORT="8888"
> MOREPORTS=""
> PUEBLOPORT="8823"
> SSLPORT="8802"
> ADMINEMAIL=your@...
> STARTDB=0
>
> I think that's all you need. You may want to adjust the variables so they are
specific to your system.

Thank you for setting me on the right path. That didn't work for me,
but defining them and exporting them in my .bashrc did. However, it's
left me with another problem. On running ./proto start I now get the
message:

(<MUCKNAME> on port <MAINPORT> from <MUCKDB>): ProtoMUCK 1.81b3 now
detaching from console.

And protomuck doesn't show amongst the active processes when I examine
them with ps. Any idea what might have happened there?

Thanks again.


--
Doklands - http://cyberinsekt.livejournal.com

------------------------------------

Yahoo! Groups Links