MJ Ray wrote:
Why would it? If the directory is group-writeable but the files aren't, Apache could delete them (IIRC), but you can avoid that by setting the sticky bit (+t) on the directory. See man chmod.
The files would need to be group-writable for Apache to be able to write to them, but the way PureFTP works (with virtual FTP users) is that all files from all users have ftpuser.ftpgroup ownership, so adding Apache to ftpgroup would give Apache write access to all FTP users' files.
I think +t might have some part in the solution, although I'm not sure of the bigger picture yet. I'm not sure what the benefit of preventing deletion is if the file can still be changed.
Maybe I'm not understanding what you're trying to do. Really, apache should be running scripts with suexec or something like that, too.
I've never found an elegant solution for Apache using suexec. Certainly it would be helpful if all virtual hosts ran as separate users (without a significant performance impact) but last I looked at that it wasn't simple to achieve what I wanted (sorry to be vague, it was some time ago I last looked at this and I don't now recall what was the issue).