RE: CVS lock script

Hi Mathew ,=20

Thanks for your reply=20
I just needed to prevent write operation will taking a backup , could you p=
lease tell me what would be the risk of taking a repository back while not =
preventing a write to it will the whole repository be corrupted or only the=
 files that was being written during backup operation=20




Thanks & BRs

Mai Saleh
IT Global Technologies & Infrastructure
Software Tools Engineer


-----Original Message-----
From: Matthew Ogilvie [mailto:[email protected]]=20
Sent: Wednesday, March 25, 2015 7:58 AM
To: Saleh, Mai
Cc: [email protected]; [email protected]
Subject: Re: CVS lock script

> Date: Tue, 24 Mar 2015 07:41:50 +0000
> From: "Saleh, Mai" <[email protected]>
> To: "[email protected]" <[email protected]>
> Subject: CVS lock script
>=20
> Hi ,
>=20
> I need to know is there any open source lock and unlock cvs repository =20
> script that can be used by corporates for free
>=20
> Thanks & BRs
>=20
> Mai Saleh

It may depend on exactly what you mean by locking a cvs repository.

In most cases it is probably easier to either manually configure existing f=
acilities (or write a short shell script to do so), rather than try to find=
, learn, and configure some third party script.

For example:

CVSROOT/commitinfo or other *info hooks might be useful for complex access =
policies.  I may have seen a reference years ago to a third party configura=
ble script you can reference from here to make it easier to configure branc=
hes/directory access, but I don't remember the name...

CVSROOT/config includes a "LockDir", which if defined would allow you to us=
e file system permissions (owner, group, mode) to control access at a direc=
tory level within the main repository, including read-only and/or no access=
.  [This is for temporary locks while CVS is processing a directory; it nee=
ds those locks even if it is doing a read-only operation...]

If you just want to have a stable version for several operations, maybe jus=
t use branches and/or tags appropriately?

If you use pserver access, you might be able to temporarily disable all acc=
ess by tweaking a line in an xinetd or inetd config file...

Or temporarily disable all access by altering the permissions on just the t=
op level directory of the repository.

                        - Matthew Ogilvie

P.S.: On a tangent, have you considered upgrading to a newer tool?
Subversion has a similar UI and is often considered somewhat more modern.  =
Also, while tools like git and mercurial have a steeper learning curve, the=
y are significantly more flexible.  The main reason I haven't gotten around=
 to to unsubscribing from this CVS list is that the traffic has dropped to =
nearly 0...