Re: problem with lock file when committing file

[Todd Denniston]

Julian Opificius wrote:
> 
> Todd Denniston wrote:
> > Julian Opificius wrote:
> >
> > <SNIP>
> >
> >>No, my primary heartache is the intended location of the lock file in
> >>the message, which is not where my configuration keeps lock files - I
> >>use /var/lock for that so I can use pserver to prevent unlogged write
> >>access to the repository.
> >>
<SNIP>
> > Q2) did you edit $CVSROOT/CVSROOT/config {to mod the LockDir variable} in
> > $CVSROOT/CVSROOT/
>   or did you do a `cvs -d $CVSROOT checkout CVSROOT` and
> > edit it in the checked out location then do a checkin? Note that except for
> > the password file, the second method (`cvs checkout CVSROOT`) is the way all
> > the files in $CVSROOT/CVSROOT should be edited.
> Yes, I did the latter.
> 
> > Q3) did you do a checkin in $CHECKOUTPATH/CVSROOT?
> I don't understand this question.

I wanted to make sure you checked in any edits you made to the config files.
i.e., does 
less /usr/local/cvsroot/CVSROOT/config
show the file containing what you expect?

> Bear in mind we're using WinCVS client on Windows, we're not using Xnix
> clients.

Should not matter from a CVS perspective (even for the problem you are
having), though the non-CVS commands I suggest you issue are generally
expected to be done on the Unix host you are using as a server. ... Let me
make sure the assumption I have from the paths you use is correct: You are
using CVS|CVSNT on a Unix host as your server, not CVS|CVSNT on a cygwin
host?
-- 
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane) 
Harnessing the Power of Technology for the Warfighter