Re: CVS errors: Unknown error 523
Vinh Cao wrote: Does anyone know this error: Unknown error 523? when our engineers do: cvs update or cvs co -r That appears to be a catch-all error handler in the server code. It also appears that you've interpreted the error vs. posting it verbatim. What is your cvs configuration (authentication method, os, cvs version, etc)? When did this start happening? -Matt ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: CVS errors: Unknown error 523
Hi Matt,
Here is our cvspserver configuration:
/etc/xinetd.d/
service cvspserver
{
flags = REUSE
socket_type = stream
instances = UNLIMITED
per_source = UNLIMITED
protocol = tcp
wait = no
user = root
group = cvsusers
server = /usr/bin/cvs
server_args = -f --allow-root=/cvs/cvsroot/Repository pserver
log_on_success += DURATION USERID
log_on_failure += USERID
disable = no
}
The OS version is Redhat 7.1 with Kernel: 2.4.2-2smp
CVS version is: cvs-1.11-3
This error was happening time to time from 6.2 for the past year and
thought migrate to Redhat 7.1 may help, but it did not.
Also cvs server is a stand alone server all users are communicating to it by
pserver. I am not cvs
admin. I am a Unix admin and these engineers told me that must be some
things to do with my
Linux server. I don't see how, because some time it works for months with
out problems and then it came back.
I just want to put this errors away if I can.
So any help from all of you would be appreciated.
Thanks,
Vinh Cao
--
-Original Message-
From: Matt Riechers [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 12, 2002 7:44 AM
To: Vinh Cao
Cc: '[EMAIL PROTECTED]'
Subject: Re: CVS errors: Unknown error 523
Vinh Cao wrote:
Does anyone know this error: Unknown error 523? when our engineers do:
cvs update or cvs co -r
That appears to be a catch-all error handler in the server code. It also
appears
that you've interpreted the error vs. posting it verbatim. What is your cvs
configuration (authentication method, os, cvs version, etc)? When did this
start
happening?
-Matt
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS errors: Unknown error 523
Vinh Cao writes: Does anyone know this error: Unknown error 523? when our engineers do: You need to find out what error 523 is on the platform where this error occurs (probably the client, and my guess would be that it's Windows). -Larry Jones Talk about someone easy to exploit! -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: CVS errors: Unknown error 523
Hi Larry, Sorry I forgot to include all OS platform. No, We are running all Red hat Linux client. These server are for xterm windows. Which mean that engineers are using exceeds to these server and do their vi, xemacs and cvs check out and do build. we have Linux cross compiler to work with all Linux server. I just wonder why cvs works for a while with no 523 errors at check out or update and then it reappear. Thanks for any help I can get out there. Vinh -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 12, 2002 11:27 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: CVS errors: Unknown error 523 Vinh Cao writes: Does anyone know this error: Unknown error 523? when our engineers do: You need to find out what error 523 is on the platform where this error occurs (probably the client, and my guess would be that it's Windows). -Larry Jones Talk about someone easy to exploit! -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS errors: Unknown error 523
Vinh Cao writes: I just wonder why cvs works for a while with no 523 errors at check out or update and then it reappear. Like I said, you need to find out what error 523 *is* on your system. Normally, /usr/include/sys/errno.h is a good starting place, but since your system doesn't seem to have a message corresponding to that number, it may well not be there. Perhaps you need to ask on a Linux list. Oh, and if either your repository or your working directory is NFS mounted, that's almost certainly the cause. -Larry Jones I don't see why some people even HAVE cars. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS Errors
SoloCDM writes: Larry Jones stated the following: SoloCDM writes: The following errors were produced with the immediate following command: make -f Makefile.cvs autoconf configure.in:147: warning: AC_TRY_RUN called without default to allow cross compiling configure.in:150: warning: AC_TRY_RUN called without default to allow cross compiling configure.in:151: warning: AC_TRY_RUN called without default to allow cross compiling They're not errors, they're warnings. Feel free to ignore them. Why are they noticeably prevalent? Because no one has ever revised CVS's configure script to support cross compiling. -Larry Jones See if we can sell Mom and Dad into slavery for a star cruiser. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS Errors
SoloCDM writes: The following errors were produced with the immediate following command: make -f Makefile.cvs autoconf configure.in:147: warning: AC_TRY_RUN called without default to allow cross compiling configure.in:150: warning: AC_TRY_RUN called without default to allow cross compiling configure.in:151: warning: AC_TRY_RUN called without default to allow cross compiling They're not errors, they're warnings. Feel free to ignore them. -Larry Jones Santa's gonna skip this block for years. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Processing CVS errors
Nope. You gotta look at standard error as well as the return code. Also cvs diff doesn't always return what you think it should either ;) donald On Thu, Dec 14, 2000 at 12:56:21AM -0800, Reinstein, Shlomo wrote: Hi, Is there some way to process CVS errors in software, other than reading the text describing them from the standard error? I have Perl scripts which make extensive use of CVS, and I'd like these scripts to be able to process CVS errors and try to recover. I can see that CVS exits with a 0 return value for success and 1 for failure, but I'd like to know (within the Perl scripts) the reason for the failure and try to process them in some way. Thanks in advance, Shlomo. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Processing CVS errors
Donald Sharp wrote:
Nope. You gotta look at standard error as well as the return code.
Also cvs diff doesn't always return what you think it should either ;)
donald
On Thu, Dec 14, 2000 at 12:56:21AM -0800, Reinstein, Shlomo wrote:
Hi,
Is there some way to process CVS errors in software, other than reading the
text describing them from the standard error? I have Perl scripts which make
extensive use of CVS, and I'd like these scripts to be able to process CVS
errors and try to recover. I can see that CVS exits with a 0 return value
for success and 1 for failure, but I'd like to know (within the Perl
scripts) the reason for the failure and try to process them in some way.
Thanks in advance, Shlomo.
Shlomo,
I have been writing Perl scripts to interact with CVS and examine the results
including output to standard error.
Some examples, completely out of context are shown below:
---
Testing if nothing present to commit or no CVS Entries present from
a cvs -nq update
$count = @result = `cvs -nq update 21`;
if ($count == 0) {
print colored ("Nothing to commit\n", 'red on_yellow');
return 0;
}
$count = @result2 = grep /update aborted/, @result;
if ($count == 1) {
print colored ("No CVS Entries presents\n", 'red on_yellow');
return 0;
}
---
This is how I get the new and previous version after a commit so that
I can do a rtag on the new version:
@result2 = `cvs -q commit -m\"$scr\" $_`;
($file) = grep /Checking in/, @result2;
$file =~ s/Checking in (.*)\;$/$1/;
($new_rev) = grep /new revision:/, @result2;
chomp $new_rev;
$new_rev =~ s/.*new revision: ([\d\.]*); previous.*$/$1/;
@result2 = `cvs rtag -F -r $new_rev $scr $file`;
print colored (" @result2", 'magenta on_white');
---
They might give you some ideas.
Dale Miller
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Processing CVS errors
Reinstein, Shlomo writes: Is there some way to process CVS errors in software, other than reading the text describing them from the standard error? The best way to do that is to use the client/server protocol rather than using the CVS command. Unfortunately, that is not a small task. -Larry Jones You can never really enjoy Sundays because in the back of your mind you know you have to go to school the next day. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
