Bugzilla – Full Text Bug Listing
| Summary: | Cannot commit to org.eclipse.releng | ||
|---|---|---|---|
| Product: | Community | Reporter: | Thomas Watson <tjwatson> |
| Component: | CVS | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | blocker | ||
| Priority: | P3 | CC: | aniefer, john.arthorne, pwebster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
|
Description
Thomas Watson
It appears the acls haven't been applied recursively. Here is a file in the releng project, note the lack of groups... johna@dev1:/cvsroot/eclipse/org.eclipse.releng/maps> getfacl ui.map,v # file: ui.map,v # owner: kmoir # group: eclipse.platform user::rw- user:kmoir:rwx user:sdimitro:rwx group::rwx mask::rwx other::r-- I don't understand the pattern here, but the net result is that some people can commit and some can't. To give concrete examples, twatson and aniefer have been unable to commit anything under org.eclipse.releng. johna and pwebster were able to commit successfully. I also seem to be unable to commit to some other projects. The server reported an error while performing the "cvs commit" command. org.eclipse.pde.build: cvs [commit aborted]: could not open lock file `/cvsroot/eclipse/pde/build/org.eclipse.pde.build/,build.properties,': Permission denied At this point it appears I can commit to things under /cvsroot/rt but not under /cvsroot/eclipse > johna@dev1:/cvsroot/eclipse/org.eclipse.releng/maps> getfacl ui.map,v
> # file: ui.map,v
> # owner: kmoir
> # group: eclipse.platform
> user::rw-
> user:kmoir:rwx
> user:sdimitro:rwx
> group::rwx
> mask::rwx
> other::r--
As I look this morning, on the same server, the ACLs look correct:
droy@dev1:/cvsroot/eclipse/org.eclipse.releng/maps> getfacl ui.map,v
# file: ui.map,v
# owner: pwebster
# group: eclipse.platform
user::rw-
user:kmoir:rwx
user:sdimitro:rwx
group::rwx
group:eclipse.platform.debug:rwx
group:eclipse.platform.releng:rwx
group:eclipse.platform.resources:rwx
group:eclipse.platform.runtime:rwx
group:eclipse.platform.swt:rwx
group:eclipse.platform.team:rwx
group:eclipse.platform.text:rwx
group:eclipse.platform.ua:rwx
group:eclipse.platform.ui:rwx
group:eclipse.jdt:rwx
group:eclipse.jdt.core:rwx
group:eclipse.jdt.debug:rwx
group:eclipse.jdt.ui:rwx
group:eclipse.pde:rwx
group:eclipse.pde.build:rwx
group:eclipse.pde.incubator:rwx
group:eclipse.pde.ui:rwx
mask::rwx
other::r--
I'm sure Matt didn't fix this since he wasn't working when this bug reported. We've configured NFS for fairly aggressive caching of file attributes, so depending on when the ACLs were put in place, it could have taken a while for all the servers to recognize them.
Please report back if (and where) commit problems are being seen.
(In reply to comment #5) > I'm sure Matt didn't fix this since he wasn't working when this bug reported. > We've configured NFS for fairly aggressive caching of file attributes, so > depending on when the ACLs were put in place, it could have taken a while for > all the servers to recognize them. Here is what we are seeing: - Files that have not been touched since Matt did the change appear to be missing the groups, as in comment #1. - As soon as someone touches the file, the acls seem to get applied (as if they are getting pulled down from the parent file on write). - However some people are not able to touch the file when in this state. For example see the acls of team.map or p2.map. They have not yet been touched since Matt's change so they don't have the ACL's populated. Some committers, such as aniefer, are not able to commit changes to these files. I've just 'touched' all of the files under org.eclipse.releng. When this problem appeared did people restart their cvs connections? -M. My commits seem to be working today. I did restart my eclipse this morning based on comment #7 (In reply to comment #7) > I've just 'touched' all of the files under org.eclipse.releng. When this > problem appeared did people restart their cvs connections? Great, this seems to have fixed the problem for org.eclipse.releng. The only other projects where we have multiple groups in the ACLs are org.eclipse.platform.doc.user and org.eclipse.platform.doc.isv. Should those projects also be "touched" to make sure the permission changes propagate? Done. -M. (In reply to comment #10) > Done. Great! I will mark as closed and let you know if we find any other problems. |