Sadhu Nadesan <[EMAIL PROTECTED]> wrote:

> What if you have no shell account access, and your ISP says something like
> 'gosh, give us a few months to evaluate this, it is a possible security
> risk, and by the way, its going to COST you..'. Are you out of luck?
> 
> Maybe not. If they allow you to install and run your own CGI programs
> using FTP, then, you can still use MC as a CGI scripting language and
> get it up and running without their help. You might need a bit of help

Wow!  Thanks Sadhu!  Now I can forget about PERL.  Probably this was
somewhere on the MC web site and I failed to read it.  Most likely, I just
failed to put 2 and 2 together.  I followed Sadhu's "how to" and got MC
working to at least the "hello world" stage in a couple minutes.  The only
snag was that I wasn't sure what the actual cgi file I wanted the mc engine
to execute:  stack uploaded from client, etc.

So for others, the cgi script is just a plain-text file with permissions set
with chmod as given in "how to" (I used chmod 755).  It can be as simple as:

#!/www/docs/public/....(rest of path).../mc
on startup
  put "hello from mc01"
end startup

Note the /mc on the end of the path in the first line to specify the full
path to the MC engine file "mc".  When this file "mc01.mt" is executed from
the shell command line, it displays "hello from mc01" on the next line.
I've used .mt as the filename extension because I seen it used for mc cgi
scripts on the list (apparently to designate a MetaTalk script rather than
an MC stack).

Rich Herz <[EMAIL PROTECTED]>


Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.

Reply via email to