11 |
|
|
12 |
--> |
--> |
13 |
<head> |
<head> |
14 |
<title>CVS--Concurrent Versions System v1.12.1.1: F. Troubleshooting</title> |
<title>CVS—Concurrent Versions System v1.12.1.1: F. Troubleshooting</title> |
15 |
|
|
16 |
<meta name="description" content="CVS--Concurrent Versions System v1.12.1.1: F. Troubleshooting"> |
<meta name="description" content="CVS—Concurrent Versions System v1.12.1.1: F. Troubleshooting"> |
17 |
<meta name="keywords" content="CVS--Concurrent Versions System v1.12.1.1: F. Troubleshooting"> |
<meta name="keywords" content="CVS—Concurrent Versions System v1.12.1.1: F. Troubleshooting"> |
18 |
<meta name="resource-type" content="document"> |
<meta name="resource-type" content="document"> |
19 |
<meta name="distribution" content="global"> |
<meta name="distribution" content="global"> |
20 |
<meta name="Generator" content="texi2html"> |
<meta name="Generator" content="texi2html"> |
98 |
<h2 class="appendixsec"> F.1 Partial list of error messages </h2> |
<h2 class="appendixsec"> F.1 Partial list of error messages </h2> |
99 |
|
|
100 |
<p>Here is a partial list of error messages that you may |
<p>Here is a partial list of error messages that you may |
101 |
see from <small>CVS</small>. It is not a complete list--<small>CVS</small> |
see from <small>CVS</small>. It is not a complete list—<small>CVS</small> |
102 |
is capable of printing many, many error messages, often |
is capable of printing many, many error messages, often |
103 |
with parts of them supplied by the operating system, |
with parts of them supplied by the operating system, |
104 |
but the intention is to list the common and/or |
but the intention is to list the common and/or |
179 |
<dt> <code>cannot open CVS/Entries for reading: No such file or directory</code></dt> |
<dt> <code>cannot open CVS/Entries for reading: No such file or directory</code></dt> |
180 |
<dd><p>This generally indicates a <small>CVS</small> internal error, and |
<dd><p>This generally indicates a <small>CVS</small> internal error, and |
181 |
can be handled as with other <small>CVS</small> bugs |
can be handled as with other <small>CVS</small> bugs |
182 |
(see section <a href="cvs_23.html#SEC188">Dealing with bugs in CVS or this manual</a>). Usually there is a workaround--the |
(see section <a href="cvs_23.html#SEC188">Dealing with bugs in CVS or this manual</a>). Usually there is a workaround—the |
183 |
exact nature of which would depend on the situation but |
exact nature of which would depend on the situation but |
184 |
which hopefully could be figured out. |
which hopefully could be figured out. |
185 |
</p> |
</p> |
372 |
<dt> <code>cvs [server aborted]: received broken pipe signal</code></dt> |
<dt> <code>cvs [server aborted]: received broken pipe signal</code></dt> |
373 |
<dd><p>This message seems to be caused by a hard-to-track-down |
<dd><p>This message seems to be caused by a hard-to-track-down |
374 |
bug in <small>CVS</small> or the systems it runs on (we don't |
bug in <small>CVS</small> or the systems it runs on (we don't |
375 |
know--we haven't tracked it down yet!). It seems to |
know—we haven't tracked it down yet!). It seems to |
376 |
happen only after a <small>CVS</small> command has completed, and |
happen only after a <small>CVS</small> command has completed, and |
377 |
you should be able to just ignore the message. |
you should be able to just ignore the message. |
378 |
However, if you have discovered information concerning its |
However, if you have discovered information concerning its |