[Top][All Lists]

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

Re: CVSUP causing locks on the database.

From: Mark D. Baushke
Subject: Re: CVSUP causing locks on the database.
Date: Fri, 27 Aug 2004 07:40:59 -0700

Hash: SHA1

Gaganinder Singh <address@hidden> writes:

> Can someone please through some light on the following message on CVS Client
> clients application.  
> "cvs commit: [05:41:10] waiting for xyz's lock in /CVS/Dev/1.0/app"
> XYZ is the system user to which all the CVS
> users are mapped using pserver to access the
> /Dev/1.0 repository. While CVSUP is running is
> it possible that it creates locks on the
> database which restricts users from getting to
> the files and folders. CVSUP is running using
> root.


Depending on your configuration, either the
/CVS/Dev/1.0/app directory or the parallel
directory represented by the CVSROOT/config
specified LockDir=/path/name directive contains a
cvs lock file that was created by another process
to ensure that the app module remains consistent
for a user write operation such as 'cvs commit'
or 'cvs tag' or 'cvs admin' command.

If the lock persists and you know that all other
read operations have completed, you may have a
stale lock in the repository. This should not
happen, but depending on the versions of cvs,
there have been bugs that could have left stale
locks around the repository. If you believe there
could be a stale lock, go and look. The lock file
will have the process-id of the process that is
holding the lock. See if that process is still
running. If it is, leave the lock alone. If it is
not, then you may need to remove that file by

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


reply via email to

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