cvs lock ..

[Gurpreet Singh (SCM)]

Hi All, 

I am facing a strange behavior related to any of the cvs operation (co /
update / rtag) on a repository some time.
The cvs oparation stops (say a tag task) and waits for the lock. 

It gives a message "waiting for <sys_user>'s lock at <CVS_File_Path>"

The tag process stucks in-between till that (the stale lock - generally a
#cvs.rfl* type)  is removed manually. 
Though I can control this at a given point of time by searching an old one
by running a script, but its not a reliable search as we cannot distinguish
between a real and a *stale* lock file.

How by other means - this can be checked so that the tagging doesnt hinders
and if the code-base size is having good number of files, then it matters a
lot.

This linux sandbox is having cvs 1.11.11 as of now.


Any inputs----Thanks in advance.

Gurpreet S