Since switching to the latest CVS development code base, I now get
different results:
$ cvs -t update build.xml
cvs update: notice: main loop with
[EMAIL PROTECTED]:/space/cvsroot
- Starting server: ssh xx.xx.xx.xx -l dhoag cvs server
S- Reader_Lock(/space/cvsroot/build)
S- Lock_Cleanup()
I've
[EMAIL PROTECTED] (Larry Jones) wrote in message
news:[EMAIL PROTECTED]...
Manually killing a server process will cause a connection reset error
at the client. If you don't kill the server process, do you still get
the client error and, if so, is the server process still running
afterwards
only choice at this time
is run the developement version of the server. Is there anything I
need to do to see the recently added log messages? Where do the
messages go? Standard out?
- Dave
[EMAIL PROTECTED] (Larry Jones) wrote in message
news:[EMAIL PROTECTED]...
David Hoag writes:
Im
But you also said, many people use this CVS server. Do the server
processes you see come and go (which implies that they belong to other
users) or do some of them stay around forever?
The processes are owned by my user id. Started when I initiate a cvs
update(or commit). They linger until
[EMAIL PROTECTED] (Larry Jones) wrote in message
news:[EMAIL PROTECTED]...
David Hoag writes:
$ cvs -version
Concurrent Versions System (CVS) 1.11 (client/server)
... more version info
$ ssh -l dhoag 192.168.0.1 cvs -version
Concurrent Versions System (CVS) 1.11
I can not commit - Here's an example session: CVS server is on
solaris, CVS client is on RedHat, Win98, or Win2k. I am behind a Nat
router when accessing the cvs server (I've change the IP of the CVS
server to protect the innocent).
$ cvs -version
Concurrent Versions System (CVS) 1.11
More information:
When I SSH to the CVS server I see many CVS SERVER processes on the
box (via ps -ef ).
This problem appears to happen only from one set of IPs. While many
people use this CVS server, I'm the only one experiencing problems (
and from only 1 location ). I have no problems with
