Cvs Error: Failed to Create Lock Directory... Permission Denied

CVS Error: failed to create lock directory... Permission denied

The lock file is being created in /var/lock/cvs/foo/ you should check the permissions of that directory.

Why is checkout permission denied on new folder creation for CVS?

Figured it out and posting the answer for posterity.

I was originally going to set the repository folder to group cvs and make it sticky via chmod g+s /app/cvs/repository/, but that is not recursive and I don't know that I want to mess with that.

Default group id (GID) was not cvs for the users. The solution is a bit of a workaround as we're using Active Directory as our account login. Luckily, we're only using this server for CVS, which makes the solution simple.

This must be done for each account and each new account.

1. Make sure the account has attempted a log-in against CVS via Eclipse/RAD (and checked out a project, perhaps). This creates the user profile under home.
2. sudo su
3. cd \home\{username}
4. Since we have nothing else going on in it, echo "newgrp cvs" >> .profile

That will set the default group to cvs for the offending accounts on log-in and I can call it a day... and eventually migrate to Git / BitBucket.

CVS Checkout issue

The lock file is being created in /var/lock/cvs/foo/ --- you should check the permissions of that directory.

cvs import: cannot make path to /opt/cvs/test_proj: Permission denied

I did not find the exact root cause but the figured out something to do with SELINUX security. I turned off SELinux on /etc/selinux/config

SELINUX=disabled

Then rebooted the server and all worked like a magic. Checkout and adding new repo works now. I am good with turning off the security for now. Since these components will be migrated to git and this server will be upgraded.
This solution is not recommended for anyone who is intended using CVS permanently.

could not open lock file: Permission denied when branching a project

The problem was that indeed the write permission on the file system was not granted for this file. Hence the error message Permission denied.

---

Related Topics