We had a discussion going on (viewtopic.php?f=43&t=4431) where we were talking about the best way to write to a local greyhole share.
As per the guidance here and here, it seems to me like you should never write directly to /var/hda/file/* directory. Here are the two quotes I'm talking about:
From: http://wiki.amahi.org/index.php/GreyholeYou should never change or delete files in the shared directories (/var/hda/files/* by default) directly on the HDA, using the terminal, or the Gnome file browser, for the shares for which you checked the Uses pool option in the Amahi dashboard.
From: https://github.com/gboudreau/Greyhole/w ... resLocallyGreyhole data should only be accessed through shares, so mounting those shares locally is an easy way to work with Greyhole data safely.
It sounds like you should always mount the shares locally, and always write to the samba mount located at /mnt/samba/*. Question: So software (like owncloud, drupal, etc...) that will be making changes to files should be pointed to use the samba location (/mnt/samba/*) not the actual share (landing zone) location... correct?
So if the bolded question above is correct... Question 2: How do we use the mounted share with something like owncloud that needs www-data user permissions to write correctly?
Example: My hard drive is mounted at /mnt/mydrive. The owncloud share/landingzone is located at /mnt/mydrive/files/owncloud. My samba share is mounted at /mnt/samba/owncloud.
If my owncloud config points to /mnt/mydrive/files/owncloud/data, everything works fine because the user permissions on the files in /mnt/mydrive/files/owncloud/data are set to "www-data:users"
If my owncloud config points to //mnt/samba/owncloud/data, owncloud complains that it doesn't have the right permissions for that directory because those folders are "myuser:users".