Re: Documentation

45 views
Skip to first unread message

Griatch Art

unread,
Apr 7, 2013, 4:48:57 PM4/7/13
to eve...@googlegroups.com
Hi and welcome to Evennia!

But no, python evennia.py -i start is correct, to put the -i as argument to the python interpreter does not make any sense.
.
Griatch

On Saturday, April 6, 2013 3:43:26 AM UTC+2, Matthew Page wrote:
The Getting Started page needs to be updated.

This should be python -i evennia.py start
python evennia.py -i start

Matthew Page

unread,
Apr 7, 2013, 5:07:18 PM4/7/13
to eve...@googlegroups.com
Well, I'm only going off of my experience getting this going using SSH.
YourCyborg@mud~evenniagame - Google Chrome_2013-04-07_15-05-33.jpg

Griatch Art

unread,
Apr 7, 2013, 6:25:27 PM4/7/13
to eve...@googlegroups.com

Putting -i before evennia.py does nothing - all you do is start the server in daemon mode, it's equivalent to just python evennia.py start.

The question is why you cannot start in interactive mode (which is what the -i switch does). I run the demo server over ssh just fine with this switch, not sure what could be wrong.

From your screenshot it looks like invoking with -i does nothing at all - that is extremely weird since it should route the output to the terminal. Do you see this behaviour also if you start the server locally on your machine?
.
Griatch

Matthew Page

unread,
Apr 7, 2013, 6:33:34 PM4/7/13
to eve...@googlegroups.com

Are you sure it's the equivalent of just doing python evennia.py start? =S

Matthew Page

unread,
Apr 7, 2013, 6:41:18 PM4/7/13
to eve...@googlegroups.com
I haven't tried running it locally on my machine yet, but I'll give it a go later.

Starkiel

unread,
Apr 7, 2013, 7:30:40 PM4/7/13
to eve...@googlegroups.com
Reading up it seems that doing python -i will start the python interpreter (these are the >>>> symbols you see), so you are right, it's not the same as just doing evennia.py start, it's just the wrong call since you are not passing any argument to evennia.py but to python directly. So either way it's definitely not the same as starting with evennia.py -i start (which you can tell from the result - it says the Server logs to a log file rather than to the terminal).

I've never seen this problem before, there are no issues running normally over an ssh connection as far as I know. I've never run the server with python -i either to be honest and that you can get it to work launching it like that but not in the normal way is quite strange indeed.  I'm intrigued now. Did you maybe redirect your stdout in your ssh window? Do you have some strange environment variables going? Seeing how it works locally will indeed be most interesting.
.
Griatch
Reply all
Reply to author
Forward
0 new messages