[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cvs [commit aborted]:

From: David Hoag
Subject: Re: cvs [commit aborted]:
Date: 14 Feb 2002 06:39:53 -0800

Larry, thanks for your patience. 

Like I said: 

"When I SSH to the CVS server I see many CVS SERVER processes on the
box (via ps -ef )."

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

It appears as if the both the server and client process is just
sitting there. 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.

>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?

- Dave

address@hidden (Larry Jones) wrote in message news:<address@hidden>...
> David Hoag writes:
> > 
> > Im guessing its related to a slow internet connection (110kb - faster
> > than dialup) or something about my provider. Any ideas where to look?
> Like I said:
> > > Look in the server's TempDir (usually /tmp) for leftover
> > > cvs-serv* directories and core files -- if there aren't any, the server
> > > isn't crashing.
> That will at least let us know whether the server is crashing or simply
> ending without sending any error message.  If the server isn't crashing,
> you might want to try running the current development version of CVS on
> the server -- I recently made a change to send any pending output to the
> client before shutting down the server.
> -Larry Jones
> It's not denial.  I'm just very selective about the reality I accept.
> -- Calvin

reply via email to

[Prev in Thread] Current Thread [Next in Thread]