summaryrefslogtreecommitdiffstats
path: root/FAQ
diff options
context:
space:
mode:
authorTar Committer <tar@ocjtech.us>2001-10-16 03:14:40 +0000
committerTar Committer <tar@ocjtech.us>2001-10-16 03:14:40 +0000
commitb0d71377c1854271b4511488422427f73d9473d1 (patch)
tree4f4efba2179225c53238aa53e933ba81100cad81 /FAQ
parent10cc9157892d7902dddde70a5b9b2046d0c376ea (diff)
downloadrancid-b0d71377c1854271b4511488422427f73d9473d1.tar.gz
rancid-b0d71377c1854271b4511488422427f73d9473d1.tar.xz
rancid-b0d71377c1854271b4511488422427f73d9473d1.zip
Imported from rancid-2.2b8.tar.gz.rancid-2.2b8
Diffstat (limited to 'FAQ')
-rw-r--r--FAQ13
1 files changed, 12 insertions, 1 deletions
diff --git a/FAQ b/FAQ
index ed0178a..45b88d0 100644
--- a/FAQ
+++ b/FAQ
@@ -1,4 +1,4 @@
-Frequently Asked Questions about rancid - last updated 20010730
+Frequently Asked Questions about rancid - last updated 20010926
1) Platform specific
@@ -20,6 +20,17 @@ A. The manual page for cvs is quite complete, but can be be overwhelming even
for someone familiar with rcs. There are some excellent resources on the
pages http://www.loria.fr/~molli/cvs-index.html
+Q. Errors are showing up in the logs like:
+ cvs [diff aborted]: there is no version here; run 'cvs checkout' first
+A. The directory was not imported into CVS properly or was not properly checked
+ out afterward, so CVS control files or directories do not exist. create_cvs
+ should always be used to create the directories and perform the CVS work.
+ If it is just the directories have been created manually, save a copy of
+ the router.db file, then remove the group's directory, use create_cvs, and
+ replace the router.db file. If the CVS import was also performed manually,
+ cd to <BASEDIR> and use 'cvs co <rancid group>' to create all the CVS
+ control bits.
+
Q. I keep receiving the same diff for a (or set of) devices, but I know the
data is not changing repeatedly. Why?
A. This is most likely either a cvs or filesystem permissions problem. Check