Koen Deforche wrote:
> Even if you can bridge it (and if I remember correctly, there is even
> a utility somewhere that does that), you still need the permission to
> keep the FastCGI/Wt process running and listening on a local socket
> (TCP or unix domain socket), can you do that ?
I had a go at this, but it's not very promising. Using the
cgi-fcgi application on my own apache server, I notice the following
issues:
A cryptic error message from Wt ("Wt internal error: Wt is not defined,
code:
undefined, description: undefined").
All the ancilliary files are expected to be in the cgi-bin directory,
not
where the Wt binary is.
If images are placed in cgi-bin, then I get the error "script not found
or unable to stat:
/blah/blah/image.jpg, referer: http://127.0.0.1/cgi-bin/blah.cgi";
None of the images show up in the resulting page.
None of the links work. The links refer back to the document root,
but the actual Wt page appears as /cgi-bin/blah.cgi
Attepting to run on the commercial hosting is even less promising. While cgi
exectuables work, I don't seem to be able to get the Wt code to run. It's
hard to know why, since I don't have access to the apache error log :-(
It could well be that the executables don't have permission to create
a local socket, but I'm not sure how I tell. (I'm guessing I would have
to instrument up the cgi-fcgi application to emit HTML error messages).
Graeme Gill.
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
witty-interest mailing list
witty-interest@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/witty-interest
