Essential CVS/CVS Administration/Troubleshooting - Revision history

Docbook2Wiki: Initial conversion from Docbook

2008-03-07T13:08:35Z

Initial conversion from Docbook

←Older revision

Revision as of 13:08, 7 March 2008

Docbook2Wiki: Initial conversion from Docbook

2008-03-07T12:42:12Z

Initial conversion from Docbook

←Older revision		Revision as of 12:42, 7 March 2008
Line 67:		Line 67:
	If you are having difficulty connecting to a repository, first check that the repository path is declared correctly. The most common mistake when checking out a new sandbox is to forget to specify the repository path at all. Another common mistake is to forget to specify the connection method if you are using a method other than ''local'' or ''ext''.		If you are having difficulty connecting to a repository, first check that the repository path is declared correctly. The most common mistake when checking out a new sandbox is to forget to specify the repository path at all. Another common mistake is to forget to specify the connection method if you are using a method other than ''local'' or ''ext''.

-	If you want to examine the data sent to or received from the server, set the ''CVS_CLIENT_LOG'' environment ~~variable''''to~~ a file name. It must be set on the client computer, and the traffic is logged in files in the current working directory named for that filename, with the suffixes ''.in'' and ''.out''. For instance, if you set ''CVS_CLIENT_LOG'' to ''cvslog'', the traffic is logged to ''cvslog.in'' and ''cvslog.out''. (Traffic to the server is logged to ''cvslog.in'', and traffic from the server is logged to''cvslog.out''.)	+	If you want to examine the data sent to or received from the server, set the ''CVS_CLIENT_LOG'' environment variableto a file name. It must be set on the client computer, and the traffic is logged in files in the current working directory named for that filename, with the suffixes ''.in'' and ''.out''. For instance, if you set ''CVS_CLIENT_LOG'' to ''cvslog'', the traffic is logged to ''cvslog.in'' and ''cvslog.out''. (Traffic to the server is logged to ''cvslog.in'', and traffic from the server is logged to''cvslog.out''.)

	The ''gserver'', ''kserver'', and''pserver'' connection methods rely on a server that is started with ''inetd''. ''inetd'' sets a limit on the number of connections per unit of time and delays further connections. If you expect heavy use of CVS, you may need to configure ''inetd'' to accept more connections per minute. Not doing so may cause ''connection refused'' error messages.		The ''gserver'', ''kserver'', and''pserver'' connection methods rely on a server that is started with ''inetd''. ''inetd'' sets a limit on the number of connections per unit of time and delays further connections. If you expect heavy use of CVS, you may need to configure ''inetd'' to accept more connections per minute. Not doing so may cause ''connection refused'' error messages.

Docbook2Wiki: Initial conversion from Docbook

2008-03-07T12:36:38Z

Initial conversion from Docbook

←Older revision

Revision as of 12:36, 7 March 2008

Docbook2Wiki: Initial conversion from Docbook

2008-03-07T12:30:30Z

Initial conversion from Docbook

←Older revision

Revision as of 12:30, 7 March 2008

Docbook2Wiki: Initial conversion from Docbook

2008-03-07T12:25:01Z

Initial conversion from Docbook

←Older revision

Revision as of 12:25, 7 March 2008

Docbook2Wiki: Initial conversion from Docbook

2008-03-07T11:52:13Z

Initial conversion from Docbook

←Older revision

Revision as of 11:52, 7 March 2008

Docbook2Wiki: Initial conversion from Docbook

2008-03-07T11:47:08Z

Initial conversion from Docbook

←Older revision		Revision as of 11:47, 7 March 2008
Line 30:		Line 30:
	When searching the Web for CVS information, you can avoid references to CVS pharmacies or curriculum vitae by using a search string like ''CVS -pharmacy -resume''or ''CVS +version''.		When searching the Web for CVS information, you can avoid references to CVS pharmacies or curriculum vitae by using a search string like ''CVS -pharmacy -resume''or ''CVS +version''.

-	When you have an error message you don't understand, you can often find an explanation by pasting the text of the error message into a web search engine. [[Essential CVS/Troubleshooting#cvs-CHP-9-EX-1\|Example 9-1]] shows an attempt to retrieve a revision that does not yet exist (at the time, the highest revision of ''Makefile'' was 1.7).	+	When you have an error message you don't understand, you can often find an explanation by pasting the text of the error message into a web search engine. [[Essential CVS/CVS Administration/Troubleshooting#cvs-CHP-9-EX-1\|Example 9-1]] shows an attempt to retrieve a revision that does not yet exist (at the time, the highest revision of ''Makefile'' was 1.7).

	<div id="cvs-CHP-9-EX-1">		<div id="cvs-CHP-9-EX-1">
Line 73:		Line 73:
	=== Root and Repository File Problems ===		=== Root and Repository File Problems ===

-	If you are in an active sandbox and are receiving an error like the one shown in [[Essential CVS/Troubleshooting#cvs-CHP-9-EX-2\|Example 9-2]], the ''Root'' or ''Repository'' file in the ''CVS'' subdirectory of the current sandbox directory has become unreadable. [[Essential CVS/CVS Administration/Repository Management\|Chapter 6]] includes an explanation of these files and what they should contain, but the simplest way to correct a problem in a sandbox is to remove and recreate the sandbox. If there are changes in the sandbox files, be sure to preserve them before removing the sandbox.	+	If you are in an active sandbox and are receiving an error like the one shown in [[Essential CVS/CVS Administration/Troubleshooting#cvs-CHP-9-EX-2\|Example 9-2]], the ''Root'' or ''Repository'' file in the ''CVS'' subdirectory of the current sandbox directory has become unreadable. [[Essential CVS/CVS Administration/Repository Management\|Chapter 6]] includes an explanation of these files and what they should contain, but the simplest way to correct a problem in a sandbox is to remove and recreate the sandbox. If there are changes in the sandbox files, be sure to preserve them before removing the sandbox.

	<div id="cvs-CHP-9-EX-2">		<div id="cvs-CHP-9-EX-2">
Line 84:		Line 84:
	Certain changes in a repository or a repository's host environment can cause the ''Root'' and ''Repository'' files in a sandbox to be out of date. Examples of these changes include a change to the repository computer's hostname, a change to the user's username, and a change in the preferred connection method. The traditional way to manage these changes is to commit and release the sandbox beforehand and create a new sandbox afterward.		Certain changes in a repository or a repository's host environment can cause the ''Root'' and ''Repository'' files in a sandbox to be out of date. Examples of these changes include a change to the repository computer's hostname, a change to the user's username, and a change in the preferred connection method. The traditional way to manage these changes is to commit and release the sandbox beforehand and create a new sandbox afterward.

-	If you do not want to create a new sandbox, you can edit the appropriate files in the sandbox. [[Essential CVS/Troubleshooting#cvs-CHP-9-EX-3\|Example 9-3]] is a small script that relies on ''bash'' and ''perl'' to change the hostname in a sandbox ''Root'' file automatically.	+	If you do not want to create a new sandbox, you can edit the appropriate files in the sandbox. [[Essential CVS/CVS Administration/Troubleshooting#cvs-CHP-9-EX-3\|Example 9-3]] is a small script that relies on ''bash'' and ''perl'' to change the hostname in a sandbox ''Root'' file automatically.

	<div id="cvs-CHP-9-EX-3">		<div id="cvs-CHP-9-EX-3">
Line 94:		Line 94:
	=== Misconfigured Access Methods ===		=== Misconfigured Access Methods ===

-	Some of the access methods require configuration. The ''pserver'' , ''kserver'', and ''gserver'' methods require configuration at the repository, and the ''ext'', ''kserver'', and ''gserver'' methods require configuration at the sandbox. [[Essential CVS/Troubleshooting#cvs-CHP-9-EX-4\|Example 9-4]] shows the error that occurs when the ''pserver'' method is used but the user does not exist in the repository's user database. [[Essential CVS/Troubleshooting#cvs-CHP-9-EX-5\|Example 9-5]] shows the error that occurs when ''kserver'' is used but the client is not compiled to support it.	+	Some of the access methods require configuration. The ''pserver'' , ''kserver'', and ''gserver'' methods require configuration at the repository, and the ''ext'', ''kserver'', and ''gserver'' methods require configuration at the sandbox. [[Essential CVS/CVS Administration/Troubleshooting#cvs-CHP-9-EX-4\|Example 9-4]] shows the error that occurs when the ''pserver'' method is used but the user does not exist in the repository's user database. [[Essential CVS/CVS Administration/Troubleshooting#cvs-CHP-9-EX-5\|Example 9-5]] shows the error that occurs when ''kserver'' is used but the client is not compiled to support it.

	<div id="cvs-CHP-9-EX-4">		<div id="cvs-CHP-9-EX-4">
Line 122:		Line 122:
	There is a common set of client and server code used by all CVS remote-access methods. The ''fork'' connection method can be used to determine that this common CVS code is functioning correctly. To determine whether Kerberos, the GSS-API, ''rsh'', or your ''rsh'' replacement are working, you can use a simple service with the same protocol as the method you are having trouble with.		There is a common set of client and server code used by all CVS remote-access methods. The ''fork'' connection method can be used to determine that this common CVS code is functioning correctly. To determine whether Kerberos, the GSS-API, ''rsh'', or your ''rsh'' replacement are working, you can use a simple service with the same protocol as the method you are having trouble with.

-	To test whether a connection problem is caused in CVS itself, try using the ''fork'' access method to create a sandbox on the same computer as the repository. If this fails, check your repository path and check that the project name you are using is valid. If both are correct, there is a problem in the CVS client and server code that should probably be reported as a bug. [[Essential CVS/Troubleshooting#cvs-CHP-9-EX-6\|Example 9-6]] shows what should happen when you test the server with ''fork''.	+	To test whether a connection problem is caused in CVS itself, try using the ''fork'' access method to create a sandbox on the same computer as the repository. If this fails, check your repository path and check that the project name you are using is valid. If both are correct, there is a problem in the CVS client and server code that should probably be reported as a bug. [[Essential CVS/CVS Administration/Troubleshooting#cvs-CHP-9-EX-6\|Example 9-6]] shows what should happen when you test the server with ''fork''.

	<div id="cvs-CHP-9-EX-6">		<div id="cvs-CHP-9-EX-6">
Line 143:		Line 143:
	If the''fork'' test shows that your repository path and project name are valid and that the common CVS server is functioning correctly, you can isolate the problem further by testing the access method with a simple program that uses the same protocol. You must do this with the protocol client you are attempting to use with CVS, and you must use the same hostname. Kerberos 4 or 5 can be tested with the Kerberos ''rsh'' replacements, and ''ext'' or ''server'' can be tested with ''rsh''. If ''ext'' is used with a replacement for ''rsh'', that replacement should be used in the test. You can test ''pserver'' with ''telnet''.		If the''fork'' test shows that your repository path and project name are valid and that the common CVS server is functioning correctly, you can isolate the problem further by testing the access method with a simple program that uses the same protocol. You must do this with the protocol client you are attempting to use with CVS, and you must use the same hostname. Kerberos 4 or 5 can be tested with the Kerberos ''rsh'' replacements, and ''ext'' or ''server'' can be tested with ''rsh''. If ''ext'' is used with a replacement for ''rsh'', that replacement should be used in the test. You can test ''pserver'' with ''telnet''.

-	[[Essential CVS/Troubleshooting#cvs-CHP-9-EX-7\|Example 9-7]] shows a successful attempt to connect to a host named ''cvs'' using the SSH protocol. SSH clients are commonly used as ''rsh'' replacements.	+	[[Essential CVS/CVS Administration/Troubleshooting#cvs-CHP-9-EX-7\|Example 9-7]] shows a successful attempt to connect to a host named ''cvs'' using the SSH protocol. SSH clients are commonly used as ''rsh'' replacements.

	<div id="cvs-CHP-9-EX-7">		<div id="cvs-CHP-9-EX-7">
Line 172:		Line 172:
	The ''-b'' is optional if you are not using OS/2, but the rest of the syntax is required.		The ''-b'' is optional if you are not using OS/2, but the rest of the syntax is required.

-	The repository server must be running a server process that can accept the protocol the replacement is using and that can run the commands sent by the ''rsh''-replacement program. To test most of these requirements, you can run a command that uses the full syntax, as shown in [[Essential CVS/Troubleshooting#cvs-CHP-9-EX-8\|Example 9-8]].	+	The repository server must be running a server process that can accept the protocol the replacement is using and that can run the commands sent by the ''rsh''-replacement program. To test most of these requirements, you can run a command that uses the full syntax, as shown in [[Essential CVS/CVS Administration/Troubleshooting#cvs-CHP-9-EX-8\|Example 9-8]].

	<div id="cvs-CHP-9-EX-8">		<div id="cvs-CHP-9-EX-8">
Line 183:		Line 183:
	</div>		</div>

-	If you need to pass a command or call an option to your ''rsh'' replacement, you can do so by creating a small script and calling that script instead of the replacement program. [[Essential CVS/Troubleshooting#cvs-CHP-9-EX-9\|Example 9-9]] shows one such script.	+	If you need to pass a command or call an option to your ''rsh'' replacement, you can do so by creating a small script and calling that script instead of the replacement program. [[Essential CVS/CVS Administration/Troubleshooting#cvs-CHP-9-EX-9\|Example 9-9]] shows one such script.

	<div id="cvs-CHP-9-EX-9">		<div id="cvs-CHP-9-EX-9">
Line 196:		Line 196:
	CVS reserves some filenames for its own uses, and other filenames are included in the default ignore list.		CVS reserves some filenames for its own uses, and other filenames are included in the default ignore list.

-	If you have a file that CVS appears to be ignoring, check the default ignore list and any ''cvsignore'' files in your repository, home directory, or sandbox. The default list is provided in [[Essential CVS/Repository Management#cvsignore\|Section 6.5.3.2]] of [[Essential CVS/CVS Administration/Repository Management\|Chapter 6]]. If the ''-I!'' option to a CVS command causes CVS to recognize the file, then you can be sure the file is in a ''cvsignore'' list. You can temporarily force CVS to recognize an ignored file by stating it explicitly as a command parameter.	+	If you have a file that CVS appears to be ignoring, check the default ignore list and any ''cvsignore'' files in your repository, home directory, or sandbox. The default list is provided in [[Essential CVS/CVS Administration/Repository Management#cvsignore\|Section 6.5.3.2]] of [[Essential CVS/CVS Administration/Repository Management\|Chapter 6]]. If the ''-I!'' option to a CVS command causes CVS to recognize the file, then you can be sure the file is in a ''cvsignore'' list. You can temporarily force CVS to recognize an ignored file by stating it explicitly as a command parameter.

	CVS uses ''CVS'' and ''Attic'' directories in the repository. CVS prevents you from using the filename ''CVS'' but permits you to create files or directories called ''Attic''. If you use an ''Attic'' directory and look in the repository, the ''Attic'' directory has files that don't exist on the trunk from the directory above it, as well as those you are currently using in your sandbox version of the ''Attic''. You should avoid using ''Attic'' as a file or directory name.		CVS uses ''CVS'' and ''Attic'' directories in the repository. CVS prevents you from using the filename ''CVS'' but permits you to create files or directories called ''Attic''. If you use an ''Attic'' directory and look in the repository, the ''Attic'' directory has files that don't exist on the trunk from the directory above it, as well as those you are currently using in your sandbox version of the ''Attic''. You should avoid using ''Attic'' as a file or directory name.

Docbook2Wiki: Initial conversion from Docbook

2008-03-07T11:44:08Z

Initial conversion from Docbook

←Older revision		Revision as of 11:44, 7 March 2008
Line 33:		Line 33:

	<div id="cvs-CHP-9-EX-1">		<div id="cvs-CHP-9-EX-1">
-	'''Example ~~III~~-54. Web searching'''	+	'''Example 9-1. Web searching'''

	bash-2.05a$ '''cvs update -r 3.2 Makefile'''		bash-2.05a$ '''cvs update -r 3.2 Makefile'''
Line 76:		Line 76:

	<div id="cvs-CHP-9-EX-2">		<div id="cvs-CHP-9-EX-2">
-	'''Example ~~III~~-55. Repository undeclared'''	+	'''Example 9-2. Repository undeclared'''

	cvs update: No CVSROOT specified! Please use the `-d' option		cvs update: No CVSROOT specified! Please use the `-d' option
Line 87:		Line 87:

	<div id="cvs-CHP-9-EX-3">		<div id="cvs-CHP-9-EX-3">
-	'''Example ~~III~~-56. Changing the Root files automatically'''	+	'''Example 9-3. Changing the Root files automatically'''

	find ~/cvs/wizzard -name Root \| xargs perl -p -i'.bak' -e "s/helit/lat/;"		find ~/cvs/wizzard -name Root \| xargs perl -p -i'.bak' -e "s/helit/lat/;"
Line 97:		Line 97:

	<div id="cvs-CHP-9-EX-4">		<div id="cvs-CHP-9-EX-4">
-	'''Example ~~III~~-57. Pserver misconfiguration'''	+	'''Example 9-4. Pserver misconfiguration'''

	bash-2.05a$ '''cvs -d :pserver:cvs:/var/lib/cvs checkout wizzard '''		bash-2.05a$ '''cvs -d :pserver:cvs:/var/lib/cvs checkout wizzard '''
Line 104:		Line 104:

	<div id="cvs-CHP-9-EX-5">		<div id="cvs-CHP-9-EX-5">
-	'''Example ~~III~~-58. Kserver misconfiguration'''	+	'''Example 9-5. Kserver misconfiguration'''

	bash-2.05a$''' cvs -d :kserver:cvs:/var/lib/cvs checkout wizzard '''		bash-2.05a$''' cvs -d :kserver:cvs:/var/lib/cvs checkout wizzard '''
Line 125:		Line 125:

	<div id="cvs-CHP-9-EX-6">		<div id="cvs-CHP-9-EX-6">
-	'''Example ~~III~~-59. Testing the server with fork'''	+	'''Example 9-6. Testing the server with fork'''

	jenn@helit:/tmp$''' cvs -d :fork:/var/lib/cvs checkout wizzard'''		jenn@helit:/tmp$''' cvs -d :fork:/var/lib/cvs checkout wizzard'''
Line 146:		Line 146:

	<div id="cvs-CHP-9-EX-7">		<div id="cvs-CHP-9-EX-7">
-	'''Example ~~III~~-60. Testing ext'''	+	'''Example 9-7. Testing ext'''

	bash-2.05a$''' ssh cvs '''		bash-2.05a$''' ssh cvs '''
Line 175:		Line 175:

	<div id="cvs-CHP-9-EX-8">		<div id="cvs-CHP-9-EX-8">
-	'''Example ~~III~~-61. Testing ssh for suitability'''	+	'''Example 9-8. Testing ssh for suitability'''

	bash-2.05a$ ssh -l jenn cvs ls /tmp		bash-2.05a$ ssh -l jenn cvs ls /tmp
Line 186:		Line 186:

	<div id="cvs-CHP-9-EX-9">		<div id="cvs-CHP-9-EX-9">
-	'''Example ~~III~~-62. ssh script'''	+	'''Example 9-9. ssh script'''

	#!/bin/bash		#!/bin/bash

Docbook2Wiki: Initial conversion from Docbook

2008-03-07T11:37:08Z

Initial conversion from Docbook

←Older revision

Revision as of 11:37, 7 March 2008

Docbook2Wiki: Initial conversion from Docbook

2008-03-07T11:31:56Z

Initial conversion from Docbook

←Older revision		Revision as of 11:31, 7 March 2008
Line 1:		Line 1:
	{{Essential CVS/TOC}}		{{Essential CVS/TOC}}
-
-
	It would be nice if CVS were perfect, but it isn't. There will be times when CVS doesn't work as expected, but with the techniques and information in this chapter, you should be able to fix the most common problems.		It would be nice if CVS were perfect, but it isn't. There will be times when CVS doesn't work as expected, but with the techniques and information in this chapter, you should be able to fix the most common problems.