Re: cvs [commit aborted]:

[Larry Jones]

David Hoag writes:
> 
> Like I said: 
> 
> "When I SSH to the CVS server I see many CVS SERVER processes on the
> box (via ps -ef )."

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?

> So, clearly my server processes are not leaving core files (since they
> are not dieing). The /tmp/cvs-serv* directories do exist, and they're
> empty.

If you're sure those are your server processes, it might be useful to
run "netstat" to find out what state the connections are in.

> It appears as if the both the server and client process is just
> sitting there.

I'm confused -- originally you said the client was ending with
"connection reset by peer" and "end of file from server" error messages,
now it appears that you're saying the client is hanging.  Is this the
same problem or a different one?  Broken connections and hung
connections are usually not caused by the same things.

> When I run the client I can use the -t option to show a
> client side trace. I was wondering if there was someway to turn on
> some server side verbose logging to help resolve my problems.

The trace is unified -- some messages come from the client, others come
from the server.

> From your previous reply it sounds as if my 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?

The messages get sent to the client, which should display them as error
messages.

-Larry Jones

If I was being raised in a better environment, I wouldn't
do things like that. -- Calvin