-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Martin Jørgensen wrote:
Today I did a lot (at least a couple) of cvs admin -kb on some graphic
files. Since I can't directly login to the server with ssh, I have to
depend on the support from where my repository is located.
So I got this (first time ever I see this):
$ cvs -q update -dP
cvs server: [03:37:36] waiting for cvs's lock in /usr/local/cvs/
s022826/bachelor2006/report/2D_model
^Ccvs [update aborted]: received interrupt signal
And I had to break with ctrl+C. Any idea how this can happen? It should
not happen I think - and annoying that I have to contact the
support-department. Perhaps suggestions on how to avoid this in the future?
This is not the same type of lock as you get with 'cvs admin -L'. These
are concurrent locks, used to prevent corruption if two people access
the repository at the same time. See
http://ximbiot.com/cvs/manual/cvs-1.11.21/cvs_10.html#SEC87 for more
information.