Mark,
Your welcome....
The favorite is the INHIBIT trigger... slap it on several actions to
prevent them...
rmelem, rmver, chevent, *pool, rmmerge, (others)....
my general rule as a vobadmin is:
"If you can get in to trouble with a command that I can not get you our of
without going to backup tape,
you cannot do that command. If you get into trouble with a command that
causes me to go to backup tape, it is my fault"
Hope this helps as well as you visiting the site... ;)
-Charles
--- VOB Corleone
"One day.. and this day may never come... I might ask you for a favor.."
A Better Solution, Inc.
----------------------------------------------------
Charles Clarke III ClearCase Consultant
A Better Solution, Inc. (770) 252-1500 x22 [phone]
50 Springridge Ct.
Newnan, Ga. 30265 (770) 252-1501 [fax]
Email:
charles@abs-consulting.com
http://www.abs-consulting.com
At 10:11 PM 1/3/00 -0600, you wrote:
>We have been running with a fairly raw installation of
>CC for the past several months. As I am learning more
>about CC, I am realizing that both the users and the CC
>admins need to protect themselves from undesired actions.
>Hence, we need to be more robust with regard to triggers.
>
>Could you please share with me what you consider to be a
>fairly standard list of triggers an organization should
>adopt?
>
>I have already visited ABS Consulting's web site
>(http://www.abs-consulting.com/abs_consulting_triggers.html) as a
>starter (thanks!).
>
>
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Sun May 06 2001 - 00:22:16 EDT