Hi,
I can confirm this bug for 3.0.11 as well. We are treating the unix permissions as a mask for the ACLs at the moment, otherwise we end up with readonly files etc etc.
I think Peters impression is correct: unix permissions get checked first and if no 'normal' user has access rights ACL's doe not get checked.
I'll try to get a log file for this if I can get around to setup a test environment.
Regards,
Bolke
================ Cut From Digest ============= Hello again,
Jeremy Allison wrote:
> On Mon, Apr 18, 2005 at 06:35:12PM +0200, Peter Kruse wrote: > >> >> bad news, my problem is not fixed with 3.0.14a > > > > The log file helped. Try this patch (applies against > raw 3.0.14a). Problem was Solaris was returning 2 in a > place I expected a 1.... >
tried it, makes no difference here. I'm neither using "force group" nor using Solaris. Sorry to confuse you, there are probably two different problems in the same thread, although the subject is valid for both. But as the Solaris issue seems to be resolved, maybe you could have a look at my bug report: https://bugzilla.samba.org/show_bug.cgi?id=2619 The bug report includes exact instructions how to reproduce it. I get the impression that the acl implementation is wrong. It looks to me that if any user doesn't have write permission then the group settings are ignored. Jeremy, if you create such a file, do you get correct behaviour?
Thx,
Peter
-- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
