lockfile problem with 2.3.1
Mark Boolootian
booloo at ucsc.edu
Mon Jul 26 18:36:14 UTC 2004
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?
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
More information about the Rancid-discuss
mailing list