Re: CVS lock issue

Hi Glasgow,

>The file is no longer there.  This error occurred on Feb 01 according
>to a log file we maintain. We just noticed that the entire module did
>not get tagged. Could it be that a subsequent process to that area of
>the module already removed the lock sometime between then and now?

If you have a long-running operation and a short operation in between,
it=E2=80=99s very possible that the first one waits.

For example:

toplevel$ cvs tag foo

On another terminal:

toplevel/long/path/to/a/subdirectory$ cvs commit -m foo filename

The commit will succeed, even if it started after the tag and
will finish before it.

Normally, though, the tag operation would wait (I think; I only
experienced this yet with two commits) and then, after the short
commit has finished and removed its lock files, continue.

But, as I said, lockfile names are not like the ones you indicated.

Good luck,
//mirabilos
--=20
  =E2=80=9CHaving a smoking section in a restaurant is like having
          a peeing section in a swimming pool.=E2=80=9D
=09=09=09=09=09=09-- Edward Burr