Jim Klimov <[email protected]> wrote:
1) If the functionality is already there for normal shares, it seems natural
to have it for any types of shares. So as to not have unpleasant surprises.
And I think it can be done as simple as not removing the .zfs/shares/name
file entry, and reusing it upon autosharing if it already exists.
(PS: having some configurability to en-/dis-able this, would also be
convenient)
This would break various rules and assumptions about the content
of .zfs/shares:
An object is created when a share is created and it is removed
when the share is removed. Assuming we were to do as you suggest,
.zfs/shares would contain an entry for every smbautohome share that
had ever been created and they would never go away.
It may not be possible to create a regular (persistent) share with the
user's name, after the user had disconnected, because of that existing
object in .zfs/shares - it will look like that share already exists.
Similarly, the smbautohome code checks for an existing, regular share
before creating a transient share. If a regular share already exists, the
smbautohome code takes no action.
smbautohome shares are filtered by the server, regular shares are not.
These transient share objects in .zfs/shares would provide a means to
get an unfiltered list of shares.
2) *IF* access to smbautohome shares can be changed during the share's short
lifetime, (that's a big "IF" :) ) then I think someone who edited the ACL
would
expect it to persist. If not, I think directory ACLs may suffice for a long
time...
ACLs on smbautohome shares would probably be per rule rather than
per share. If you were to change the ACL, it should probably change
the ACL on the rule rather than for an individual user - unless you had
a rule per user.
Let me think about how we could support this.
Alan
_______________________________________________
cifs-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
