I want to work for Jay! :-)
But seriously, he is right because if you don't have the knowledge and the
tools to do the job, you are just going to look bad. Being tied into the
admin loop is a critical success factor. My only problem with all of this is
that doing effective Process Consultation and Process Engineering isn't
usually done by the admin team. (Poor process is where most large scale
softwrae development efforts fail these days.)
But Jay's points are well taken and we should all strive to communicate the
importance of getting what we need to do the job right.
Good luck all!
Bob Aiello
> -----Original Message-----
> From: Mark Keil [SMTP:Mark.Keil@cportcorp.com
> Sent: Wednesday, January 26, 2000 3:47 PM
> To: cciug@iname.com; Aiello, Bob (Exchange)
> Cc: cciug@Rational.Com
> Subject: RE: [cciug] vobadm vs root
>
>
>
>
> Bob/All,
>
> Thanks for the reply....
>
> You touched on a related subject that I think might be
> sort of hot... Does the Clearcase admin need root
> priv's??? You mentioned for example start/stop CC.
>
> -YES, backups, moving vobs, fix permissions problems,
> -rebuilding broken .identity dirs, moving vobs/views,
> -fixing system cointext issues, starting/stoping...
>
> My management is wanting to take su away and I'm
> resisting!!!!
>
> -You will be less efective, and less timely without it.
>
> -If they do take it away, consider another company.
> -At one company I interviewed with a while back
> -they didn't give clearcase archetects/release engineers root
> -they were an immediate reject.
>
> Thanks, Jay
>
>
> -As for the vobadm/root question, BOTH are required
> -I keep 4 process shells on my unix vob server
> -at most times, 2 as myself, 1 vobadm, and 1 root.
> - 4 contexts for 3 different classes of tasks.
>
> -Mark
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
***********************************************************************
Bear Stearns is not responsible for any recommendation, solicitation,
offer or agreement or any information about any transaction, customer
account or account activity contained in this communication.
***********************************************************************
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Sun May 06 2001 - 00:22:38 EDT