aharleycpl

Send private message

You must be logged in to send a private message.

Group membership

Activity

  • Interesting that the username and group name is nobody for httpd processes.  That from what I see is a pseudo name and not meant to own any files or folders: The nobody user is a pseudo user in many Unixes and Linux distributions. According... view reply
  • Thanks for your reply.. it makes some sense.  When tried the chown for wwwrun:www it comes back with an invalid user.  I am not quite sure how to find the correct name to use and so far haven't found a good reference on how to look it... view reply
  • Here is what I am running apache 2.2.27 php 5.6.30 elgg 2.3.3 running on a vps server.  One main site and one small site i use for testing. only other potential hog of resources running on the vps is red5 to dish up some video chat...
    • One possibility to find out: with the "top" command you get a list of running processes. The Apache processes should be named "http" or "http-prefork". The listing includes the user of the process. Group of the process might not be enabled. But you can do that by pressing SHIFT-F and then enable group (you might also need to move the group up for better visibility in the process table).

      If top doesn't work you can google for the Apache user including the Linux distribution's name in the search (as user/group is mostly a matter of the Linux flavour used).

    • Interesting that the username and group name is nobody for httpd processes.  That from what I see is a pseudo name and not meant to own any files or folders:

      The nobody user is a pseudo user in many Unixes and Linux distributions. According to the Linux Standard Base, the nobody user and its group are an optional mnemonic user and group. That user is meant to represent the user with the least permissions on the system. In the best case that user and its group are not assigned to any file or directory (as owner). This user is in his corresponding group that is (according to LSB) also called "nobody" and in no other group.

    • Apache can be configured to run under a specified user and group. But the Apache config is a matter your webhoster is responsible for in the first place. On a VPS you will likely be able to adjust the Apache config on your own, if you want Apache to not run as nobody. Then you would likely also have to update all files and directory ownership accordingly or there might be permission issues. Then you could "chown -h" also the cache symlink accordingly. I can't give you any detailed help how to change the Apache config accordingly as it might be different regarding where to change it. Maybe in /etc/apache2/http.conf is some info in the comments with regard to the where the user and group is specified. For example it's done in /etc/apache2/uid.conf on my server.

      Or you could just do the "chown -h" on the symlink to nobody:nobody for testing. If it doesn't fix the issue, the problem needs to be fixed in some other way anyway. And if you don't want the ownership to stay as nobody:nobody you can just delete the symlink again.