[cvsnt] Re: Locking out specific projects...

Lehman, Curtis CLehman at carrieraccess.com
Fri Sep 17 20:46:28 BST 2004


Hi Glen, 

Thanks for the suggestion. I gave it a try, but the examples are based on
1.3 lock server. I tried entering the commands like they had them, but it
seems that the lock server no longer supports the recursive command. 

Tony, you mentioned the acl commands in CVS. I tried those a while back, but
was not able to get them working. For some reason my server thinks it's a
stand alone server even though it's not. (Even though I couldn't get it
work, thanks for the help and time on that issue.) 

Thanks,
Curtis Lehman

-----Original Message-----
From: Glen Starrett [mailto:grstarrett at cox.net]
Sent: Thursday, September 16, 2004 4:36 PM
To: cvsnt at cvsnt.org
Subject: [cvsnt] Re: Locking out specific projects...

Lehman, Curtis wrote:
> In-between steps 1 and 4 could be several hours, but after step one the
code
> base will be broken until step 4 is done. How can I lock out all the users
> from checking out or committing changes to the project?  I don't want to
> stop the CVS service on the server because that blocks the other unrelated
> projects in the company from continuing to use CVS. I thought about
writing
> a pearl script to call from one of the CVSROOT files like commitinfo, but
> that doesn't stop the checkout. Any suggestions?

Check out the LockServer page in http://www.cvsnt.org/wiki/LockServer ,
there's a tip there that might do what you're looking for:  A way to
lock all the files in a particular module until you cancel the lock.

--
Glen Starrett
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt




More information about the cvsnt mailing list