Jay,
It is all relative to your environment. We don't lock our vobs all year
round even
many of our builds going on at night or day time. I guess, the config spec
sufficient
enough to ensure the data integrity.
How to lock your Unix vob from NT ?
First, you need to import your Unix vobs into NT region by using "Region
Synchronizer"
from NT desktop. Once all vobs have been imported, you can do things as you
do on Unix.
Ex. ct lock vob:\myvob
Hope its help.
Ieng
-----Original Message-----
From: owner-cciug@rational.com [mailto:owner-cciug@rational.comOn
Behalf Of cciug@iname.com
Sent: Thursday, January 27, 2000 4:30 PM
To: cciug@rational.com
Subject: [cciug] Administering Unix VOBs from NT
Hello,
Can anyone tell me, is it common practice to lock a vob/branch, etc before
doing a build to ensure what
is being built? Does anyone use other methods.
Relatedly, I'm not very adept at NT and would normally
lock a VOB from Unix (since that is where the VOB
server is) using the vobadm account. How does one go
about locking the Unix server VOB from NT and what
setup is required?
Thanks, jay
(I always put my name in lowers when asking an NT
question because I'm quite ignorant)
---------------------------------------------------
Get free personalized email at http://www.iname.com
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Sun May 06 2001 - 00:22:40 EDT