I would try setting the "shellCommand" property- I've seen that needed on various configurations before. See the docs for a description, but basically you need to set it to a valid shell script binary, i.e. /bin/tcsh

HTH

Brian

Ok, this was good in theory. But shell seems "dead" with the linux engine we are using.

We can log into the Linux server in Austin from Hawaii via SSH and issue a shell command like this

ls -al ## obvious and simple

But if we run this from inside an xTalk CGI, nothing happens:


on startUp put ("ls -al") into temp get shell(temp) put it into var1 put "Content-Type: text/plain" & cr put "Content-Length:" && the length of var1 & cr & cr put var1 end startUp

var1 is empty.

The version we are using is linux metacard engine version 2.4 build 2... but docs indicate shell commands should work find for that version.

Any hope?

This is working on OSX with the latest version of Revolution. Is anyone aware of what the status of shell was with v2.4 b2?

Sannyasin Sivakatirswami
Himalayan Academy Publications
at Kauai's Hindu Monastery
[EMAIL PROTECTED]

www.HimalayanAcademy.com,
www.HinduismToday.com
www.Gurudeva.org
www.Hindu.org
On Dec 26, 2003, at 7:55 PM, Jan Schenkel wrote:

--- Sannyasin Sivakatirswami <[EMAIL PROTECTED]> wrote:
OK more info on this one:

We suspect it is because Revolution is not able to
accept an https
URL... it return "Invalid URL"  a search on the
lists doesn't turn up
much....

Hope there is a work around and we are missing
something simple...

## where we are trying to get the returned web page
from verisign

put URL
"https://payflowlink.verisign.com/payflowlink.cfm?
[snip]


It's in the keyword 'https' -- libURL doesn't support secure http yet, as that requires SSL.

We could use the onboard "curl" shell command but
the credit card info
is going to end up in the server logs... not ideal.

Thanks!


Not necessarily ; while I was in college I spent time with some 'creative minds' who had come up with the following trick to erase their steps on the Solaris server : make the shell history file for the user read-only for the owner with 'chmid 111' ; this effectively prevents the shell from writing to its history file.

Hope this helped a bit,

Jan Schenkel.

=====
"As we grow older, we grow both wiser and more foolish at the same time." (La Rochefoucauld)


__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree
_______________________________________________
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution


_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution



_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution

Reply via email to