Ok folks, I have seen numerous posts about this. I did a new install of Links 2.0. All the permissions on the files are set. All the calls to perl on the first line, are correct /usr/bin/perl on my box. Everything seems to be right. All the paths in links.cfg are correct. I have looked at it so long I am blue in the face. The admin tools all work perfectly. Not a problem. However, search.cgi, add.cgi, rate.cgi, jump.cgi (basically all the regular CGIs) don't work. I have tried expanding out the require to links.cfg with no success. So, I even went as far as to attempt to run it from the command line (with produced the standard CGI error output). So, I edited db_utils.pl and commented out the line that gives the error if the .cgis are run from the command line and the darn things produce valid HTML code with Content-type headers. Why oh why then, don't they work through the browser then! Any ideas? I know I am rambling but I am at my wits end. This is becoming extremely frustrating, especially since I forked out the $210 cdn for the product. PS. My OS is linux....

Do you have ALL the .cgi files in the same directory that is password protected? If so, you need to move the .cgi files except the admin.cgi file to another non-password protected directory.

That is all I can think of based on the other things you've tried.

Regards,

Eliot Lee

Thanks Elliot. The jump.cgi, search.cgi, etc. are all in the /cgi-bin directory, while the admin.cgi and all its cronies are in the admin directory which is protected via http authentication. I have gone as far as to remove the http authentication to try to see if this is the problem, and I still get the same error. Thanks for the answer though....unfortunately, I still have the same problem.

Fraser

Don't know what to tell you other than re-installing Links again...make no modifications to the scripts, and see if it runs.

Regards,

Eliot Lee

Thanks it didn't work. It took me 5 installs to get it this far....

Welp...seems to be a problem with your server configurations and your Perl set-up...I would check both and see if there are any problems.

Good luck!

Regards,

Eliot Lee

Found the problem. Because the httpd runs as a different user for a few virtual hosts, for security reasons, the permissions on my cgi-bin directory were 775 which, due to the use of STRICT in the code, was causing the error. As soon as I set my cgi-bin directory permissions to 750, everything works like a charm.

Frustrating, but at least now I know the cause....

Fraser