[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Getting lock during commit stalls cvs ci
From: |
Harry Putnam |
Subject: |
Re: Getting lock during commit stalls cvs ci |
Date: |
Wed, 01 Feb 2006 16:34:15 -0600 |
User-agent: |
Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux) |
Jim Hyslop <address@hidden> writes:
>> And it is root doing the commit anyway. I've enabled-rootcommit at
>> compile time since its a single user machine, root and user are always
>> the same thing.
>
> From a security perspective, running as root for general purpose
> activities is a Really Bad Idea.
How is that true with a single user home machine?
>> Anyone know what the error means?
>
> It's not a permission problem. Check for any stray files or directories
> in the repository with names starting #cvs.rfl, #cvs.wfl, or #cvs.lock,
> and remove them (make sure you aren't running any cvs processes, first,
> though).
That was the first thing I did. Well not exactly. I searched for
*.lock which of course, did not find those little buggers.
find /usr/local/cvsroot -name '#*' was a better choice and found the
culprit.
/usr/local/cvsroot/base/reader/home/reader/\
scripts/perl/#cvs.rfl.reader.16434
Thanks.