Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We use CVS to hold many of our configuration files for applications. We have been trying to standardize on a location to hold each of them, and when initially setup, they work great ;)

our basic process is this.. as user APP1
mkdir /configs/
cd /configs
cvs get Prod/client/application

This creates a nice set of subdirectories with all our config files, and in theory, is as easy to update as going to the /configs directory, and typing "cvs update Prod".

However, we have lots of developers and admins that seem to forget to SU to the user APP1. so for the initial checkout of the files, it might be done under a different user.. or perhaps they navigate there as themselves, and type:

cd /configs
cvs get pre-Prod/client/application
cvs get Prod/client/application2

Now, nobody else besides them can seem to use CVS with that set of directories.. I can change the owernership of the files, but is there a way to not lock the CVS folder stuff to a certain user?

Maybe I should be asking this on Stack Overflow, but this is more for the administration of the repositories (or to help me fix it all)

share|improve this question

You can try the following:

  1. Create a dedicated user APP1.
  2. Restrict write access to user APP1 in the /config directory.
  3. Create a script that checks updates /config directory from CVS with the APP1 credentials.
  4. Ask all your developers and admins to use the script to update the /config directory.
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.