Gaffer

This command should tell you who “owns” the Apache (httpd) process in your Linux system:

ps -ef | grep httpd

Notice that the two commands are separated by a vertical bar (pipe) — the output of the first program is fed as input to the second program for further processing

Also, when you run chown, you need to be in the appropriate directory, and specify the correct files and/or directories.

Hope that helps,

Tony

Hi Mike,

Thanks very much for the quick reply!

I have just made a donation to your paypal.

My problem with “WAITING FOR” was solved by chown from “root” to “apache”.

I originally had 0755 but changed to 0777 because the “CAPTCHA PHP requirements test” told me:

Directory /captcha-temp/ Directory Unwritable (fix permissions). Permissions are: 0755 Fixing this may require assigning 0755 permissions or higher (e.g. 0777 on some hosts. Try 0755 first, because 0777 is sometimes too much and will not work.) Fixing the actual problem is recommended, but you can uncheck this setting on the plugin options page: “Use CAPTCHA without PHP session” and the captcha will work this way just fine (as long as PHP sessions are working).

–> You might consider adding a sentence to check the ownership of the files, must match the user that runs httpd — your codex link helped me understand that aspect.

However, I still get 500 “internal server error” in Apache’s access_log if I click to post and have not filled in the Captcha. Here is a copy-and-paste from the beginning of the log entry:

[10/Nov/2010:21:26:40] “POST /blog/wp-comments-post.php HTTP/1.1” 500 1236 “http://www.glassblower.info/blog/151/si-captcha-anti-spam-for-blog-comments/” “

I’m not overly concerned about the 500, but did want to point it out to you, maybe you can see if reproducible on another system? My guess is the problem is more likely to be in the WordPress code than in the Captcha code.

Many thanks again,

Tony