DSO configuration

Dualnames

• January 20, 2014 04:21

Hello, This isn't actually an issue but more of some clarificiation on how DSO creates files from PHP scripts. WordPress and other CMS's can have issues with their update functions whether it be WordPress itsself or the plugins. When the files are created, they are created as nobody:nobody. I guess my main question is why would this cause issues? Is it because nobody can't write to files or maybe Apache can't run the files if they are nobody:nobody? Also, one last thing. What are the correct ownership and permissions for files and folders with the DSO handler? To my understanding it should be user:nobody for the ownership and files should be 664 and folder 775. Any input is greatly appreciated :)

• 

  cPanelMichael

  • January 20, 2014 17:04

  Hello :) Here is a document that answers your questions about the use of "nobody" ownership with DSO and what permissions are required: [url=http://docs.cpanel.net/twiki/bin/view/EasyApache/Php/RequestHandling#DSO]EasyApache: PHP Request Handling To note, if you plan to use DSO, you should consider using Mod_Ruid2. It's documented here: [url=http://docs.cpanel.net/twiki/bin/view/EasyApache3/ModRuid2] mod_ruid2 Module Thank you.

  0
• 

  Dualnames

  • January 22, 2014 10:14

  Hello Michael, "Also, files created by PHP scripts will be created by nobody That means files and directories that will receive the output must be writable by the system user nobody." So does this mean for a file to be overwrite it would require permissions on that file to be 666 or 664?

  0

Please sign in to leave a comment.