OK... thanks for spelling that out for a newbie like me... I continued to get nothing in the Command Shell of webmin so I used telnet to telnet to the server and it all worked as expected in the shell there. I must be a problem with webmin (or maybe webmin is not meant to be used in this way...)
Anyway, I got all the expected results... the 'print x' resulted in answer >>> What does this suggest to you? Should I try to run the required commands for mailman in the telnet session rather than from the command shell in webmin? Thanks again... Mike -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Sapiro Sent: Saturday, 19 November 2005 12:13 PM To: [EMAIL PROTECTED]; mailman-users@python.org Subject: Re: [Mailman-Users] setting up mailman Mike Wharton wrote: > >I am a total newbie when it comes to linix and am learning as I go so I may >not have fully understood your suggestion. I typed these into the command >line in the webmin interface on my server. That's the problem. Sorry I wasn't more specific about what to do. Here's another try: At the shell (command line) prompt, type 'python' and see the following where '$' represents the shell prompt to which you're typing: $ python Python 2.4.1 (#1, May 27 2005, 18:02:40) [GCC 3.3.3 (cygwin special)] on cygwin Type "help", "copyright", "credits" or "license" for more information. >>> The '>>> ' is the interactive prompt from Python. The other stuff is from Python and probably won't be exactly the same. then type "x = raw_input('Prompt: ')" in response to the prompt and it should look like >>> x = raw_input('Prompt: ') Prompt: at that point. Type "answer" (followed by enter) and you should get another '>>> ' prompt to which you type "print x". If you are not seeing the '>>> ' prompt, or you see it, but it is immediately followed by another shell prompt without your typing anything, there is some issue in the shell or the invocation of python such all input requests are receiving an end_of_file 'automatic response. This could be caused for example by 'python' being aliased in your shell to 'python </dev/null', although I have no idea why that would be. You can type 'alias' at a shell prompt to see all the command aliases. -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/mwharton%40presdata.com .au Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
