On Tue, Feb 17, 2009 at 9:10 AM, Naga <nagat...@gmail.com> wrote: > On Monday 16 February 2009 00:59:41 Kevin O'Gorman wrote: >> I've got a low-use CGI script on my web server. Aside from web >> crawlers, I usually see at most a few hits a week from >> people who share my hobby. >> >> I just found out it's been down for an unknown period of time because >> my Apache no longer does CGI scripting. >> I can't even get it to run the simplest possible C program. > > Not sure if this is related to your problem but I had a similar issue that was > caused by having "threads" as a USE flag for Apache. This has the effect that > the mod_cgi.so module isn't built, but the mod_cgid.so one is. > > /Regards > Naga > >
Problem solved. It wasn't i18n, and it wasn't Python. Apparently somewhere along the line, apache started to provide a command-line argument to CGI programs. At least my Python script was getting an empty string in argv[1]. The script is picky about that, but had old code to handle it that worked only for the command-line. It did not expect to have any arguments at all when running as CGI. After fixing up error handling, and training it to ignore empty string parameters, the script runs just fine. Check it out at http://hex.kosmanor.com/hex-bin/board if you like the game of Hex. It's a hobby thing. ++ kevin -- Kevin O'Gorman, PhD
