info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Lock question


From: Mark D. Baushke
Subject: Re: Lock question
Date: Thu, 08 Nov 2007 18:36:07 -0800

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Simon Renshaw <address@hidden> writes:

> The lock file look like #cvs.rfl.castor-srvr4.benchmarkcanada.com.19844
> and is owned by simon. That's my username.

If process 19844 is still running on your CVS server, then you might
want to kill it and remove the lockfile. If the process is not running,
you may just remove the lock file.

The lockfile is created when you are doing a checkout or other read-only
operation (e.g., cvs update).

> Each dev use his own username and since I'm not a dev I don't usually
> commit stuff.

Sure, but write locks are of the form #cvs.wfl.host.dom.ain.123456

> But, there is a Windows machine running Cruisecontrol with CVSNT 2.5.03
> that uses my name to check CVS for changes.
>
> Could it be the cause of the lock?

Yup.

        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (FreeBSD)

iD8DBQFHM8eXCg7APGsDnFERAgSGAJ9yVK7iVaBFQSIEqGVOjGWeoBQnLgCaA4I6
ES3CQIJhFBkWUZnXNo0BB/k=
=YscY
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]