[cvsnt] Unable to commit
nospam at nospam.net
Wed Mar 12 04:50:45 GMT 2008
An old user works on all computers, both old and new. New users don't
work on either. The CVSROOT for a working user and non-working user is
Both working and non-working users can perform checkouts. Non-working
users just can't commit anything. I ran cvsdiag on both old and new
boxes and while logged in as both old and new users. Everything looked
okay; no reported errors.
I just realized that the error message I'm getting from the cvs on the
client-side also references this strange filename ",Login.cs,". Here is
a copy of my exact error:
>cvs commit -m "" Login.cs
Checking in Login.cs;
new revision: 1.5; previous revision: 1.4
cvs [server aborted]: could not open lock file
Why is CVS adding a "," prefix to the filename? I tried this from a
brand new box, joined it to the domain, then logged on as working user
and non-working user. Same results.
I don't understand how this is even happening. Are you sure there's not
some code similar to what you suggested? :)
Arthur Barrett wrote:
>> Is this a bug in CVSNT?
> Well not exactly no - we added a code path a while back that does this:
> if new_user(claims_to_be("nospam.net")) // owned by hormel foods
> // existing users claiming to be from nospam.net are OK
> // this will really confuse them!
> The problem is occurring with new users only - it's clearly
> environmental since the above code would just be silly.
> I assume new users also use new PCs? Start looking there - does a 'new
> user' on an 'old users' PC work OK? Compare the results of cvsdiag on
> the old and new users PC.
> What is the CVSROOT the new user is using? What is the CVSROOT the old
> user is using?
> If the two users are using the same PC and getting different results
> then go looking in the registry HKCU or environment.
> If the clients are running on the same PC as the server then re-run your
> tests from scratch with the clients on a different PC to the server.
> Finally you can enable 'allow clients to trace server' in the server
> control panel and run the commit on both clients with 'cvs -ttt ci' and
> compare the results (don't send the traces to the newsgroup - they will
More information about the cvsnt