lockfile problem with 2.3.1

[john heasley]

Mon, Jul 26, 2004 at 11:36:14AM -0700, Mark Boolootian:
> 
> Folks,
> 
> I've just upgraded to 2.3.1, following the instructions per UPGRADING.
> When I fire up rancid-run, I find that it queries all the routers just
> fine, but then hangs complaining about the lockfile (log entries below).
> Any ideas what this complaint is telling me?

my best guess is that either
- another cvs process is running which legitimately has a lock on this dir

or

- a cvs process was running with the dir locked at the time you copied/moved
  the repository

or

- a cvs process was abruptly terminated and left the stale lock behind

iirc, the lock file names begin with .# (see cvs(1)) and will be in the
repository heirarchy...where ps and lsof will help you find the owner
process.  if there is no process, simply removing the file is OFTEN ok.
again, see cvs(1).

> thnx,
> mb
> 
> ---
> 
> cvs commit: [17:38:40] waiting for rancid's lock in /usr/local/rancid/var/rancid/CVS/Backbone
> /configs
> cvs commit: [17:39:10] waiting for rancid's lock in /usr/local/rancid/var/rancid/CVS/Backbone
> /configs
> cvs commit: [17:39:40] waiting for rancid's lock in /usr/local/rancid/var/rancid/CVS/Backbone
> /configs
> cvs commit: [17:40:10] waiting for rancid's lock in /usr/local/rancid/var/rancid/CVS/Backbone
> /configs
> cvs commit: [17:40:40] waiting for rancid's lock in /usr/local/rancid/var/rancid/CVS/Backbone
> /configs
> cvs commit: [17:41:10] waiting for rancid's lock in /usr/local/rancid/var/rancid/CVS/Backbone
> /configs
> cvs commit: [17:41:40] waiting for rancid's lock in /usr/local/rancid/var/rancid/CVS/Backbone
> /configs
> cvs commit: [17:42:10] waiting for rancid's lock in /usr/local/rancid/var/rancid/CVS/Backbone
> /configs