[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: CVS Core on AIX
From: |
Arthur Barrett |
Subject: |
RE: CVS Core on AIX |
Date: |
Fri, 18 Nov 2005 09:32:48 +1100 |
Derek,
> This isn't a problem from other UNIX boxes and it's not a problem from
> Eclipse. The only time a core file is created is a result of using
> WinCVS / CVSNT
In that case please refer it to the CVSNT newsgroup:
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
or
news://news.cvsnt.org/support.cvsnt
You will probably want to run the test with 2.5.03 client before
submitting the bug report.
Also see this FAQ's about how to submit a bug report:
http://www.march-hare.com/cvspro/faq/faq2.asp#2z
>Here's a trace:
>CVSROOT: address@hidden:/source/CVS (password authentication)
>cvs login
>
>Logging in to :pserver:address@hidden:2401:/source/CVS
>
>***** CVS exited normally with code 0 *****
There are two problems with this trace:
1. it is not a trace
2. it doesn't crash
To find out how to create a trace - read this:
http://www.march-hare.com/cvspro/faq/faq2.asp#4L
Eg:
cvs -ttt login
Also creating two client side logs (use $CVS_CLIENT_LOG, for
instructions see previous link). Create one log ($CVS_CLIENT_LOG) on
windows with CVSNT 2.5.03 and one on Unix (can't do it from Eclipse).
This will allow the developers to compare a trace from a client that
causes the server to crash to one that doesn't.
If you do not use a recent client such as CVSNT 2.5.02 or CVSNT 2.5.03
then you will probably get no response.
> As a result we now have a high dependency on CVSNT / WinCVS.
It'd be good to subscribe to the CVSNT (and WinCVS) newsgroups and use a
recent version ;)
> We're considering trying to move the repository to
> a Suse box and get off the AIX box altogether,
> but that's a project in and of itself with no
> guarantees.
If you are going to consider that move then I recommend using CVSNT
server on Suse (free/GPL, etc) since you are committed to CVSNT client.
You could also try compiling CVSNT server on AIX - but it's never been
done before...
Do not send any more info about this problem to the info-cvs list, send
it to the CVSNT list. You have identified it as a CVSNT client problem.
Regards,
Arthur Barrett