On Tuesday 30 September 2003 17:42, Wayne Call wrote: > When attempting to execute a cvs commit command, I receive the > following error: > > cvs commit: failed to create lock directory for '\mnt\ .....' > > I have created a mount using the smbmount command as follows: > > smbmount //WORKGROUP//VOL1 /mnt/file1 -o username=wcall > > The mount is for a network drive on a Windows NT Server. The "cvs > commit" command attempts to check in files from a Linux Machine > directory to the network drive. It failes because it cannot create a > lock. I believe the lock cannot be created because a guest user > cannot create locks on the mounted network drive. > > Any suggestions?
You're right in that you have to have write permission in order to create the locks. Can you put the lockdir somewhere writable? I'm assuming this is a shared FAT drive....... >From the manual: http://www.cvshome.org/docs/manual/cvs-1.11.7/cvs_18.html#IDX283 ------------ LockDir=directory Put CVS lock files in directory rather than directly in the repository. This is useful if you want to let users read from the repository while giving them write access only to directory, not to the repository. It can also be used to put the locks on a very fast in-memory file system to speed up locking and unlocking the repository. You need to create directory, but CVS will create subdirectories of directory as it needs them. For information on CVS locks, see Several developers simultaneously attempting to run CVS. ------------ Regards, Mike Klinke P.S. You may want to spend some time in the CVS archives reading about all the knashing of teeth when it comes to using CVS on a mounted file system like this.... http://mail.gnu.org/mailman/listinfo/info-cvs -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
