Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!cmcl2!nrl-cmf!ames!xanth!manes From: manes@xanth.UUCP (Mark Manes) Newsgroups: comp.os.vms Subject: Re: [Richard Steinberger : Star Wars] Message-ID: <3296@xanth.UUCP> Date: Tue, 10-Nov-87 17:27:15 EST Article-I.D.: xanth.3296 Posted: Tue Nov 10 17:27:15 1987 Date-Received: Sat, 14-Nov-87 04:09:01 EST References: <8711091436.AA25227@ucbvax.Berkeley.EDU> Reply-To: manes@xanth.UUCP (Mark Manes) Organization: Old Dominion University, Norfolk Va. Lines: 21 Summary: Are you sure you want to do this? I am afraid I can't help you with your specific problem. However, I do have a suggestion. Don't bother trying to take the privs away, if these programmers need it to do there daily work, then let them have it. Good Management is the key, not restricting access to YOUR programmers. Once a priv is given away, it is next to impossible to take it back, at least that is what my experience has shown me. It can create great political trouble. Especially if you are new. As far as the problem goes, why not just have a duplicate copy of the software running, with duplicate files, etc. for testing with your programs, and then YOU or somebody moves new stuff to the application accounts? Well it was just an idea :-D -mark= Guest of ODU University, System Manager Academic Computing Norfolk State University