modwest

I thought I’d better rephrase my question with some technical specifics:

• At Modwest, scripts run as the user that owns the script. The scripts live in the user’s homedir.
• So, at Modwest, a script by has write (or overwrite) access to files.

Since the WordPress codebase contains many chmod() calls, I am wondering if there is a circumstance in which it does a chmod g+w or chmod 777 (or similar) that sets additional write-permission bits on folders or files.

We are seeing multiple customer instances of WordPress spontaneously malfunction because of permissions changes.

Thanks samboll — a recursive grep does turn up instances of chmod(), but I don’t know the internals well enough to conclude anything:

$ svn info | grep URL
URL: https://svn.automattic.com/wordpress/tags/2.7.1

$ grep -irl chmod * | wc -l
     35

Check your error log for details.
I assume you’re getting ‘403 Forbidden’. Could be file permissions. Here are some other ideas:
https://www.modwest.com/help/kb1-144.html

Infrastructure – what’s the bottleneck for WP then? CPU due to MySQL? I/O?
The blog I am considering converting from MT gets 900+ comments per post (in the space of minutes or hours), and MT cannot keep up.

Anyone? Can WordPress handle this sort of traffic?