An odd question has come up during setup of a new web server here.
I'm used to being able to specify this in httpd.conf (at least, it works on our production server):
User www
Group www
... then use the standard UNIX user administration tools to maintain group memberships for user www, and have the web server's permissions respond appropriately to those memberships.
But on this new installation I'm finding that the Group directive is all that matters, and it doesn't seem to care what groups the operating system thinks the www user belongs to. Say, if user www is a member of group
foo, and a directory has permissions 2770 and ownership
root:foo, then the web server can't write to that directory -- unless I change the "Group" directive from
www to
foo.
Have I missed another directive, either in a configuration file or when building the executable?
* edit *
Oops, solved - the problem was in the user setup. Somehow I'd munged the www user account such that its initial login group was something other than www. It was still a member of the www group, but that wasn't good enough. Now with www having www as its initial group, and belonging to a few other groups, it behaves as expected and the same as on the production server.
