[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
CVS 1.11.2 lock behavior
From: |
Dan Peterson |
Subject: |
CVS 1.11.2 lock behavior |
Date: |
Fri, 14 Jun 2002 14:45:04 -0700 (Pacific Daylight Time) |
Has the locking behavior changed between 1.11 and 1.11.2?
Specifically, we've noticed locks for an entire tree seem to hang around
until the entire tree has been modified. The 1.11 behavior seemed like it
would only lock a specific directory at a time.
In other words, the "observed" behavior for 1.11 when doing some write
operation (like a tag or rtag) on an entire tree was:
cvs tag FOOBAR /foo/bar
for each directory under /foo/bar
lock directory
perform tag operation
unlock directory
done
and for 1.11.2 is SEEMS like it's doing something more like this:
cvs tag FOOBAR /foo/bar
for each directory under /foo/bar
lock directory
done
for each directory under /foo/bar
perform tag operation
done
for each directory under /foo/bar
unlock directory
done
The big problem with this is that for large source trees (2000+
directories) it can take a long time to do the operation and during that
time, the entire tree is essentially locked.
- CVS 1.11.2 lock behavior,
Dan Peterson <=