[OpenIndiana-discuss] Persistent permissions

[Dormition Skete (Hotmail)]

Why do you have two “g:”’s in there?  

It should be user (u), group (g), and other (o).

Here are some examples from what I have used.

setfacl -R -m g::rwx /home/Documents
setfacl -R -m o::0 /home/Documents

I’m no expert at this, either, but it looks to me like you’re trying to set the group to two different things with the same command.

I think what you are trying for is this:

setfacl -m u:myguest:rwx,d:g:guest:rwx guest

I have to run right now, though.  I’m sorry.

I hope this helps.

fp


On Aug 20, 2014, at 12:45 PM, Michelle Knight <michelle at msknight.com> wrote:

> Sorry, should have included an example command...
> 
> setfacl -m g:myguest:rwx,d:g:guest:rwx guest
> 
> 
> 
> On Wed, 20 Aug 2014 12:32:27 -0600
> "Dormition Skete (Hotmail)" <dormitionskete at hotmail.com> wrote:
> 
>> Does OpenIndiana have facl?  If it does, “setfacl" should do what you
>> are looking for.
>> 
>> http://www.computerhope.com/unix/usetfacl.htm
>> 
>> 
>> 
>> 
>> On Aug 20, 2014, at 12:14 PM, Michelle Knight <michelle at msknight.com>
>> wrote:
>> 
>>> Hi Folks,
>>> 
>>> I'm not sure how to do this under ZFS, but here goes...
>>> 
>>> I have a ZFS share/pool which is accessed via SMB and also SFTP. A
>>> number of different users can put (and move) files between
>>> directories and even create directories in some cases.
>>> 
>>> I would like any file which is uploaded or moved (or new directory
>>> created) ... to obtain the permissions and levels of the directory
>>> that it is moved/copied to, regardless of what it had before it was
>>> moved, and regardless of the account or permissions of the account
>>> that did the operation, whether it be done via SMB or SFTP. Also,
>>> any directory then created will have the same influence on any
>>> files created/copied in to it.
>>> 
>>> At the moment, I am using a script which will go through the
>>> directory structures and forcefully re-write the ownerships and
>>> permissions of every file, but this obviously has an impact as if
>>> there is a copy operation going on when the script hits that
>>> particular area, it can re-write the permissions on a file and halt
>>> the copy process because of a permissions error.  This technique
>>> also has the problem that some users have to wait for the script to
>>> run, because they won't have access until the file/directory
>>> permissions have been re-written.
>>> 
>>> Is there any more elegant way of doing this please?
>>> 
>>> Michelle.
>>> 
>>> _______________________________________________
>>> openindiana-discuss mailing list
>>> openindiana-discuss at openindiana.org
>>> http://openindiana.org/mailman/listinfo/openindiana-discuss
>>> 
>> 
>> 
>> _______________________________________________
>> openindiana-discuss mailing list
>> openindiana-discuss at openindiana.org
>> http://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> _______________________________________________
> openindiana-discuss mailing list
> openindiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss