Files ownership on Linux servers issue

cnisvcs

Perch
There are three common ways to upload/delete files on a webserver:
-- via ftp client,
-- via CMS,
-- via WebShell file manager in Hsphere CP.

About a year ago, when I developed a site for the client, files uploaded with ftp client used to receive accountname/accountname user/group ownership. Files uploaded the other two ways received httpd/httpd ownership.

Currently files uploaded with any of these three ways belong to accountname/accountname.

At this point I have bunch of folders and files that I can't do anything about due to ownership mismatch.

Q1: Is there a way I can fix this issue myself (e.g. PHP script running chown command on files in question) or I have to go through trouble ticket?

Q2: Is this change a result of making the PHP interpreter to run as the fastcgi module? I noticed in CP under PHP is the note: PHP Mode: php_php5 (php_fastcgi5). Just curious.

Q3: In CP, right under PHP, there is "Advanced PHP" option. What does this option do? The yellow popup says that it requires the PHP to be turned off first. If this option changes the PHP5 from fastcgi to original way, I could switch temporarily, remove the files, switch back and re-upload them quickly via ftp.

Please advise. Best regards to Jodo staff!
 
It is due to moving to fastcgi, best to put in a ticket and we will chown the files to the fastcgi user, yes it happened due to the switch to fastcgi, but it should have changed permissions as well, possibly some files got skipped in that.

Overall the fastcgi means is much better :)
no need to mess with the advanced, it fact doing that sometimes makes apache not reload properly and we have to go hunt down the site making apache not load....has happened a few times on web14 and web15 I know.
 
Just following up on this thread: I've had this issue drive me crazy on a bunch of joomla sites where everything uploaded has suddenly become owned by httpd and subsequently completely off-limits to the account owner. The first trouble ticket I sent in on this was given the response that there was nothing to be done about it, but help desk could reset the files for me for now. That's simply not tenable in the long (or short) term. They seemed to know nothing about the fastcgi issue, but I'm trying to understand the fix you're mentioning above, Stephen: chown-ing the files to the fastcgi user will perhaps solve the problem for the current set of files that are all screwed up -- but what happens the next time my client adds an application module to his site, or uploads an image that then needs to get resized? I can't keep coming back to all y'all to get stuff reset every other day? If this means no hosting joomla or drupal on hsphere-based reseller accounts, so be it, but pls let us know where we stand on this.
 
I'd also like to know a definitive answer to this.

When we develop a custom module and use the installer - Joomla or Word Press - we can not edit those files again.
We have to submit a ticket to reset permissions. Although this is not a huge problem, it's definitely a hassle if we're doing multiple installs....
 
I'm also curious about this - I've done a couple wordpress installs in the past two weeks, and sometimes the ownership are httpd, sometimes they are the user name...and for some reason sometimes I need to open the permissions to 777 in order to upload through wordpress, but not other times.

I'd love to know clearly how I should install wordpress in order to retain the cms utility without having to open the permissions all the way up.
 
I have opened a trouble ticket (Ticket ID: EJL-81594-606) in order to get clarification about the best practice for installing wordpress. I am not willing to turn a site loose using 777 permissions, but for some reason some wordpress installations require this while others don't.

I'd like to know if it's a matter of user/group ownership, if it varies from server to server, or if there is a "proper" method for installing wordpress that will allow the cms to function properly at 755 or more restrictive permissions.

I look forward to a response.
 
Right on, just keep me posted. I love wordpress, but it loses a lot of the utility if I can't let a client operate without changing the permissions each time.
 
Back
Top