Date: Wed, 18 Jul 2001 11:28:35 +1000
From: Timothy Shimmin <tes@boing.melbourne.sgi.com>
To: Andi Kleen <ak@suse.de>
Cc: Federico Sevilla III <jijo@leathercollection.ph>,
   Linux XFS Mailing List <linux-xfs@oss.sgi.com>
Subject: Re: [PATCH] Re: chacl question
Message-ID: <20010718112834.R11622@boing.melbourne.sgi.com>
References: <Pine.LNX.4.21.0107172125090.467-100000@kalapati.leathercollection.local> <20010717165543.A21737@gruyere.muc.suse.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <20010717165543.A21737@gruyere.muc.suse.de>; from ak@suse.de on Tue, Jul 17, 2001 at 04:55:43PM +0200
Sender: owner-linux-xfs@oss.sgi.com
Precedence: bulk

On Tue, Jul 17, 2001 at 04:55:43PM +0200, Andi Kleen wrote:
> On Tue, Jul 17, 2001 at 09:29:01PM +0800, Federico Sevilla III wrote:
> > But it says:
> > 
> > chacl: "u::rwx,g::,o::,u:jijo:r-x,m::r-x" is an invalid ACL specification.
> 
> You cannot have multiple 'u' specifikations.
Yes you can :)
You can't have multiple USER_OBJ ACE specifications (i.e. 'u::')
but you certainly need multiple USER ACE specs (hence the multiple 'u').
As already pointed out, you need permissions specified for all ACEs
(i.e. for GROUP and OTHER as well).

> 
> Similar problems have also annoyed, annoyed me enough to produce the following
> patch which adds somewhat usable error reporting to libacl.
> 
> Just apply it below cmd/chacl and get at least usable error messages.
> 
> It also fixes one bug in the manpage.
Thanks.
I'll have a look over it soon, 
run the qa tests and check it in...:)

--tim