Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!ucbvax!rcb@mcnc.org@rti-sel.UUCP
From: rcb@mcnc.org@rti-sel.UUCP
Newsgroups: mod.computers.vax
Subject: Re: (none)
Message-ID: <8702181612.AA18186@rtisel>
Date: Wed, 18-Feb-87 11:12:04 EST
Article-I.D.: rtisel.8702181612.AA18186
Posted: Wed Feb 18 11:12:04 1987
Date-Received: Thu, 19-Feb-87 21:11:42 EST
References: <8702151825.AA01209@ucbvax.Berkeley.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: rti-sel!rti-sel.UUCP!rcb@mcnc.org (Random)
Organization: Research Triangle Institute, RTP, NC
Lines: 9
Approved: info-vax@sri-kl.arpa

In article <8702151825.AA01209@ucbvax.Berkeley.EDU> esj@ufl.CSNET (Eric Johnson) writes:
>  I am a student and a 'assistant' system manager of a vax750. Let me give
>you a hint as to how a new vax system manager could deal with a knowledgeable
>student. HIRE HIM/HER. Most of us will work slave hours for slave wages, just
>to have a vax to take care of. The benifits of this are patently obvious. 

This was exactly the policy when I worked at Elon College. If somebody managed
to get access to the priviledged accounts, we would hire her/him with that 
persons first task being to close the security hole they used to gain access.