[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CVS lock script

From: Erik Christiansen
Subject: Re: CVS lock script
Date: Wed, 25 Mar 2015 20:16:09 +1100
User-agent: Mutt/1.5.21 (2010-09-15)

On 25.03.15 08:33, Saleh, Mai wrote:
> Hi Mathew , 
> Thanks for your reply 
> I just needed to prevent write operation will taking a backup ,

The following assumes that the repository is on a unix box of one
flavour or another, and that it is adequately backed up, so that a
fumble is not fatal.

If the repository is given e.g. the group "developers":

# chgrp -R developers <path_to_repository>

and all developers allowed access gain that by being made members of
that group, then they can temporarily be locked out with:

# chmod g-wx <path_to_repository>

I.e. On a directory, execute permission is navigate permission.

When the backup is complete:

# chmod g+wx <path_to_repository>

If the repository is owned by an exclusive account, then that can be
used instead of root, and that would be less risky in the event of

Over several decades, the only measure I took to ensure a static
filesystem during backups was to have cron run them at 3 a.m.
when none of my developers would be there. It is, however, trivial to
add the two chmod commands to a backup script.

You just need to be there in the morning to run the second chmod
manually if something goes wrong halfway through the backups.
(Though a few hours of delay in being able to check in is usually OK)


manual, n.:
A unit of documentation. There are always three or more on a given item.
One is on the shelf; someone has the others.
The information you need is in the others.               - Ray Simard

reply via email to

[Prev in Thread] Current Thread [Next in Thread]