Re: a commiting problem

[Paul Sander]

This means that the RCS file cannot be updated for some reason.  The way
it works is that the ,file, is created, the modifications are written into
it, and then it's renamed to a new file,v file.

There could be any number of reasons why the ,file, cannot be updated,
but it's not because you don't have write permission into the repository
(because the CVS directory lock had to be created before this point).
Most likely reasons are that an orphan ,file, already exists and is owned
by another user.  You might also be running out of disk space.

If you remove the file and it magically reappears, then it means that
someone is concurrently updating the file.  If it's happening while you
own the CVS lock, then it means that someone is updating the file outside
of CVS (i.e. using RCS directly).

--- Forwarded mail from address@hidden

I have a simple file, dtbsom.cxx.  After making some code changes to it i
decide to check it in, so i say:
cvs commit dtbsom.cxx
vi opens for me and I add my log message and go to save my changes in the
usual way, CTRL ZZ.(for vi)

The error message i receive is cryptic.

                Checking in dtbsom.cxx;
                /mounts/sun16_cvs/etc /etc /  < -- dtbsom.cxx
                new revision:1.2; previous revision: 1.1
                cvs [commit aborted]; could not open lock file
'/mounts/sun16_cvs/etc/etc/etc/,dtbsom.cxx,': File exists

Puzzled i go into the cvs repository and notice that in the corresponding
directory to my local directory is a file
by the name of: ",dtbsom.cxx,"   (notice the commas before and after the
name).  
I try to delete this file via rm -f dtbsom.cxx. But to no avail.  The file
magically reappears.  My attempts to commit the file are met with the same
error messages: 'could not open lock file' and 'file exists' even after I go
direct into the cvs repository to delete it.

--- End of forwarded message from address@hidden