On 04/29/2015 12:50 PM, Chris wrote:
> Mhhh, maybe your PHP process (which is used by ownCloud for reading and
> writing stuff) is running on another user than www-run which could explain
> why you're able to read but not to write stuff.
>
> Have a look at:
>
> https://doc.owncloud.org/server/8.0/admin_manual/installation/installation_wizard.html#setting-strong-directory-permissions
>
> how to get the actual user running your php scripts.
While I'm not sure how a change uid might occur in this setting/setup, I
ran that test and hot the 'wwwrun' that Apache runs under on my machine.
If one is to traverses from /srv/www/htdocs/owncloud/data/anton/files
though the symlink folder
lrwxrwxrwx 1 wwwrun www 22 Apr 21 MyDocuments -> /home/anton/Documents/
one actually gets to files like this
-rw-rw-r-- 1 anton users 73127 Jun 21 2007 Famous_People_Quotes.odt
and also
drwxrwxr-x 20 anton www 1736 Apr 26 21:29 /home/anton/Documents/
Note that they are rw by group users.
Now I had added wwwrun to that group
# id wwwrun
uid=30(wwwrun) gid=8(www) groups=100(users),8(www)
Linux is using Berkeley Semantics rather then UGS semantics so that
means while wwwrun would create a file wwwrun:www it should be able to
use the group settings.
The ~anton/Documents directory is group www so it should be able to
write there, and the group semantics should, in fact do, allow the files
to be read.
Given that I've made these changes I don't understand why an Apache task
running as wwwrun can't write to a directory that is group www and group
writeable, and can't write the files there.
--
Each success only buys an admission ticket to a more difficult problem.
-- Henry Kissinger, Wilson Library Bulletin, March 1979
_______________________________________________
User mailing list
[email protected]
http://mailman.owncloud.org/mailman/listinfo/user
