This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: web/1653: gdb cvs HEAD version.in stuck at 2004-04-17
- From: mec dot gnu at mindspring dot com (Michael Elizabeth Chastain)
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 16 May 2004 21:08:00 -0000
- Subject: Re: web/1653: gdb cvs HEAD version.in stuck at 2004-04-17
- Reply-to: mec dot gnu at mindspring dot com (Michael Elizabeth Chastain)
The following reply was made to PR web/1653; it has been noted by GNATS.
From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: gdb-gnats@sources.redhat.com
Cc: cagney@redhat.com
Subject: Re: web/1653: gdb cvs HEAD version.in stuck at 2004-04-17
Date: Sun, 16 May 2004 17:00:50 -0400 (EDT)
[Andrew, could you take this PR? It's a problem on the sourceware side]
This is a permission problem with /sourceware/snapshot-tmp.
Here is the relevant part of log/update-cvs-version:
2004-04-17 -d /cvs/src co src/gdb/version.in
1c1
< 2004-04-17-cvs
---
> 2004-04-16-cvs
cvs commit: [00:00:04] waiting for gdbadmin's lock in /cvs/src/src/gdb
cvs commit: [00:00:34] obtained lock in /cvs/src/src/gdb
Checking in version.in;
/cvs/src/src/gdb/version.in,v <-- version.in
new revision: 1.1038; previous revision: 1.1037
done
2004-04-17 -d /cvs/src co src/gdb/version.in
2004-04-17 -d /cvs/src co src/gdb/version.in
2004-04-17 -d /cvs/src co src/gdb/version.in
2004-04-17 -d /cvs/src co src/gdb/version.in
2004-04-17 -d /cvs/src co src/gdb/version.in
2004-04-17 -d /cvs/src co src/gdb/version.in
2004-04-17 -d /cvs/src co src/gdb/version.in
2004-04-17 -d /cvs/src co src/gdb/version.in
2004-04-17 -d /cvs/src co src/gdb/version.in
2004-04-17 -d /cvs/src co src/gdb/version.in
2004-04-17 -d /cvs/src co src/gdb/version.in
2004-04-17 -d /cvs/src co src/gdb/version.in
2004-04-17 -d /cvs/src co src/gdb/version.in
2004-04-17 -d /cvs/src co src/gdb/version.in
2004-04-17 -d /cvs/src co src/gdb/version.in
2004-04-17 -d /cvs/src co src/gdb/version.in
2004-04-17 -d /cvs/src co src/gdb/version.in
2004-04-17 -d /cvs/src co src/gdb/version.in
mkdir: cannot create directory `/sourceware/snapshot-tmp/update-cvs-version.24377': Permission denied
/home/gdbadmin/ss/update-cvs-version: line 26: cd: /sourceware/snapshot-tmp/update-cvs-version.24377: No such file or directory
2004-04-17 -d /cvs/src co src/gdb/version.in
mkdir: cannot create directory `/sourceware/snapshot-tmp/update-cvs-version.15198': Permission denied
After update-cvs-version fails to make its temporary directory, it keeps
running in the current directory. Remember, at this point there are *two*
instances of update-cvs-version running, one for the head, and one for
the branch! They are both failing to create unique temporary directories,
so they are both running in the same current directory and colliding.
It looks like the branch always wins the collision; I don't quite
understand that mechanism.
Gerald Pfeifer reported the same permission problem here:
http://sources.redhat.com/ml/overseers/2004-q2/msg00206.html
Re: GCC snapshot generation and machine load
He worked around the problem by creating a permanent subdirectory in
/sourceware/snapshot-tmp with mode 2755. Chris Faylor said that this
is the right thing to do. I looks like update-cvs-version needs a
similar permanent subdirectory and a script change to use it.
Michael C