4
gediminasbyt wrote:
Quote:
There are couple steps for it. Check as what user apache is running by issuing a command:
ps aux|grep apache
First column on left will show as what user apache is running. Most of the time it will be apache.
Go to your XOOPS install directory and issue:
ls -al
It will show something like:
drwxrwxrwx 13 username1 username2 4096 Nov 1 14:23 directoryname
(P.S. username2 is the owner of those files)
If username1 is not the same as in previous command then go to your XOOPS install directory and issue this command:
chown -R usernameinstep1 *
if you want to change the owner of the files then you do
chown -R usernamestep1:usernamestep1 *
Gediminas
This is a major thing so I like to make sure I understand you right.
I checked
ps aux|grep apache
first on my local linux box then on my hosted server. On my hosted server apache is running as root. Is it still save do do this?
Following would change all folders to be owned by root
chown -R root *
and this would change all files to be owned by root, right?
chown -R root:root *
Let me see if I understand this right.
If I transfer ownership of folders and files to what ever apache is running as then I can run cache and c_template as chmod 755 and don't have to run it as 777. Is this correct?
Now my understanding why people install phpsuexec is. They want to prevent users in a shared box to access each others php files. phpsuexec needs much more cpu resourses so if you don't have shared hosting it is better to run with out phpsuexec, right?
I could go on with quetions but if don't want to over due it.
Thank for your help
