[Top][All Lists]

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

Re: CVS server process still running long after command is executed

From: Jeeva Sarma
Subject: Re: CVS server process still running long after command is executed
Date: Thu, 5 Sep 2002 12:03:18 -0700 (PDT)


How do I log the output from cvs?My server is FreeBSD.

I am not very familiar with system administration.

cvs is not running as a daemon.I don't understand how
the remote client accesses cvs.
Is it thro' rshd, which is a daemon?
So to trace cvs process,should I trace the inetd
daemon which inturn starts the shell daemon(rshd)?If
so,what specific commands should I look for?

Pls give me some pointers as to where to start.

Also if someone can explain how cvs client and server
communicate and how inetd knows to call cvs when a
client runs a cvs command?

Thanks a lot,
Jeeva Sarma

--- Mike Ayers <address@hidden> wrote:
> Jeeva Sarma wrote:
> > Hi all
> > 
> > I have received no replys for this question whish
> I
> > posted 2 days ago.
>       The primary reason for that would be that you gave
> no information 
> from which an answer could be derived.  First, check
> if your server is 
> set up so that it logs all its output - if not,
> reconfigure it to do 
> so (on Unix systems, just use ">" output redirection
> to file; if you 
> are using a Windows server, check the manual for
> that system to see 
> how, or if, this can be done).
>       Once your server logs its output, just do your
> usual until the 
> process hangs, then check the log.  If you are on a
> Unix server, kill 
> the CVS process (do NOT `kill -9` it!) to flush the
> file.  Now read 
> the end of the file - that should give you some idea
> of what the 
> problem is.
> > Have no one ever faced this problem?Can someone
> tell
> > me atleast the reason for the cvs processes not
> > dying?It only happens sometimes,not always.The
> server
> > eventually freezes.
>       Sounds like you've got a resource comsumption
> problem.  Off the top 
> of my head, I'd guess that the problem is not CVS,
> but a CVS script 
> (commitinfo, taginfo, etc.) going infinitely
> recursive or somesuch. 
> If you are using scripts, check your process list to
> see if any of 
> them are running when CVS hangs.  If so, there's
> your culprit.
> /|/|ike

Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes

reply via email to

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