[Top][All Lists]

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

Re: waiting for user's lock

From: Mark D. Baushke
Subject: Re: waiting for user's lock
Date: Thu, 26 Feb 2004 20:21:40 -0800

Hash: SHA1

Courier <address@hidden> writes:

> I need some help on cvs acting up on my cvs server. Here is what happening:
> My users are just doing cvs diff or cvs log or cvs update, then they got
> back cvs error: waiting for builder's lock and cvs server tell exactly
> where is cvs PATH file that cause problems. The file name like:
> #cvs.wfl.stein.29903, stein is cvs server name, 29903 is the process id.
> One of my developer did ps -ef on cvs server and found this:
> #ps -ef | grep cvs
> 29903 ?        D      3:33 cvs -f --allow-root=/cvs/cvsroot/Repository
> pserver
> So we are looking into D on ps and thinking that may be I/O problems?
> or even network cause cvs system slow down?

A wfl lock is a write lock such as is used when a user is committing a
change to a file or files in a particular directory of the repository.
It is temporary and is released when the operation has completed. As
long as a process matching the pid on the lock file is present, you are
probably okay.

> But what I need from you is: does cvs cause problem or some thing else?


> My cvs server is Redhat9.0 with cvs version from redhat: cvs-1.11.2-13.

This is valuable. Thank you for including it.

Your users doing read-only operations like 'cvs diff' may find that
using 'cvs -n diff' will have better performance for them.

You may find that your users are taking a long time to manually write
the log messages when they do a commit. Suggesting to them that they
write their log message before issuing the cvs commit command and then
pasting the log message into the cvs template or bypassing the template
using the

    cvs commit -F logmsg

form of the cvs commit command may let you see less time being spent in a
cvs lock state.

> Also all other build servers we have is P4 1.2 GHZ, but cvs server is :
> dual Xeon P4. Not sure that help, but i throw it out there just in case
> some one may ask.
> I did search older archive and found some responded back from Larry about
> LockDir may be some where else. We do not have LockDir. Cvs server does
> lock by itself.
> Can some one help?

The problem of write locks gets easier in the development branch of cvs
with promotable locks. You may wish to wait for cvs-1.12.6 as I believe
that there is a case where a core dump occurs with cvs 1.12.5 right now
(it is fixed in the CVS TRUNK).

        Good luck,
        -- Mark
Version: GnuPG v1.2.3 (FreeBSD)


reply via email to

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