-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mark Shellenbaum wrote:
|> What ACL have you setup on the root directory of share?  What does
|> "ls -dV /tank" show
|
|> and what is the permission of files you have created via CIFS?  What
|> does "ls -V <file>" show.

Apologies this was originally posted to the previous poster and not the
list. Getting used to a new MUA

Ok I've tried to reduce this as simply as I can to see where my problems
lie.

If I reset the perms to trivial and apply the following:

chmod -R A+group:staff:rwxpAWCo:allow tank

Then it works as expected and the user in the staff group can perform
actions with the same rights as the owner. However once a directory is
created it assumes perms like so:

d---------+  2 matthewh staff           2 May 27 07:44 test/subdir
        user:matthewh:rwxpdDaARWcCos:-------:allow
~     group:2147483648:rwxpdDaARWcCos:-------:allow

Which means that administering the files in the future becomes very
difficult. What I want to do is something like this:

chmod A+group:staff:rwxpAWCo:fd:allow tank

To allow all newly created files to be managed fully by the staff group.
~ This doesn't work and while I can create a directory, I can't set the
name, rename it, delete it or anything else.

This just doesn't seem to make sense. There must be a simple way to do
what I want but ACLs make the job much more difficult than I think it
should be.

I've been reading through the zfsadmin pdf file and it looks like what I
want to do should work, yet it doesn't.

Can anyone please supply some examples of how they solved a problem like
this?

Thanks in advance

- --
Matt Harrison
[EMAIL PROTECTED]
http://blog.genestate.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iEYEARECAAYFAkhB7u0ACgkQxNZfa+YAUWEMCgCg1EREytbhkXvGuirLD4lZqhCJ
MdgAoIFWZUbgkK8OTSOmXBa4lcHlrngc
=VYZe
-----END PGP SIGNATURE-----
No virus found in this outgoing message.
Checked by AVG.
Version: 8.0.100 / Virus Database: 269.24.4/1475 - Release Date: 30/05/2008 
14:53
_______________________________________________
opensolaris-discuss mailing list
[email protected]

Reply via email to