Re: default ACLs disappearing when used with CVS?
Scott Mcdermott <[email protected]> Wed, 11 Aug 2004 12:30:15 -0400
| Newsgroups | gmane.linux.file-systems.acl.devel |
|---|---|
| Message-ID | <[email protected]> |
Andreas Gruenbacher on Wed 11/08 10:10 +0200: > > How can the files and directories start appearing > > without any extra ACL information than the old POSIX > > model? Wouldn't setting default ACLs on ALL directories > > in repository cause all new filesystem objects to > > inherit their effect? > > Default ACLs will inherit down from the parent directory > when new objects are created, yes. As far as I know there > is no code in CVS that would explicitly set ACLs. definitely not in my version. That's why I'm so perplexed by this; all access to the filesystem occurs through pserver, which doesn't explicitly set any ACLs. Yet I have files and directories showing up without them in directories that definitely have a default ACL set. Sounds the same as the the problem the other guy reported in response to my email. > Could it be that directories are created somewhere else > and into the CVS repository in some cases? This could > explain the effect, even though it would be a weird thing > to do. No, don't see how that could happen. I think there may be some kind of bug which causes the default ACL not to inherit for some reason in some odd circumstance. Is there a sysctl I can set that will turn on verbose logging of ACL propagation or anything like that? Also is there any reason that my kernel 2.4.25+pre8+ea_acl_nfsacl-0.8.65 does not have sufficient ACL patch version to take care of some already known bug? _______________________________________________ acl-devel mailing list [email protected] http://acl.bestbits.at/mailman/listinfo/acl-devel