View Full Version : logs_cgi
03-10-1999, 05:37 AM
I cannot get the hang of this. going into logs_cgi and executing 'script' appears to record all the shell activity into a file called 'typescript' (some of which looks like garbage when viewed with pico). So how does one debug cgi pgms? If the logs_cgi dir is empty, does that mean no errors have been produced?
I'd rather have a bottle in front
of me than a frontal lobotomy
03-10-1999, 01:45 PM
script, is a Linux utility that starts a logging session of what you type at the command line... I use it when testing things like a clients FTP program, and they can see the exact steps I take to verify all is working...
script is really not used for debugging cgi, it's just a facility to transcript everything you type and the results that are returned...
The garbage characters you see are the extended ansi codes that create the colored prompt... I haven't tryed to figure out how to strip those, I do it the lazy way and just search/replace all the garbage, stripping the high 8-bit characters...
The logs_cgi would contain extended information from a CGI 500 error... It is both logged to your normal error log, and the extra debugging info is in your script log...
I never thought about the name clash between the filename choice of 'script' and program name 'script'... They are both totally unrelated to each other...
If the script log is empty, then that means that either you have no errors, or that the script breaking is so fatal that Apache can't even trap the error and log it to 'script' logs...
--A rose by any other name--
vBulletin® v3.6.8, Copyright ©2000-2013, Jelsoft Enterprises Ltd.