RE: [cobalt-users] cgiwrap problem running cgi script

["Tom Cameron" <tomcameron@xxxxxxxxxxxxxxx>]

Ursula Saturday, 23 November 2002 3:13 PM

=> > It seems extraordinary to me that there
=> > are not debugging logs
=> > at all for cgiwrap.
=>
=> Debugging cgi is simple to set up, the following is
=> from the KB article:
=>
=> There is an effective utility you can use to debug CGI
=> scripts, using the CGIWrapper feature. This is what
=> you need to do:
=>
=> Telnet into your server as root.
=>
=> Edit the following file:
=>
=> /etc/httpd/conf/srm.conf
=>
=> # The following lines add debugging features for CGI
=> Action cgi-wrapperd /cgiwrapDir/cgiwrapd
=> AddHandler cgi-wrapperd .cgid
=> AddHandler cgi-wrapperd .pld
=>
=> Save the file, and restart the web server:
=>
=> /etc/rc.d/init.d/httpd.init stop
=> /etc/rc.d/init.d/httpd.init start
=>
=> Copy or rename your CGI scripts with the extension,
=> cgid or pld, and execute the script through your
=> browser.
=>
=> This will provide debugging information about the
=> script, and aid in locating what the cause of a
=> failure of the script.

Ursula, thanks for this, but actually all this does is pass the scripts to
the cgiwrapd script which is in fact what I already did by calling it
directly throught the URL http://domain.com/cgiwrapDir/cgiwrapd/test.cgi. As
I mentioned in a previous post, this returned no information at all as if
the script is not being called at all. So I am no closer to finding out why
this is happening.

All the same it is a neat way of setting up the debugging rather than the
URL method.

Tom