| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 218.1 | But we only wanted to install some programs | CURRNT::GREEN_K | Well it nearly works | Wed Mar 01 1989 16:39 | 23 |
| It is clearly not practical for a user to book a testinstall account
for several days and have it to the exclusion of all others. We
know from our own experience today that occasions will arise when
a testinstall account is needed by others at short notice.
The system which appears to have evolved during today is that when
the original 'owner' of Testinstall can spare it for an hour or
more, they inform the calldesk of the person who is to 'borrow'
it, and the inform that person of the password. When that person
has finished with it, they inform the calldesk that they are handing
it back, and inform the original owner that they have finished.
Presumably the original owner would then wish to change the password.
Could we have confirmation that this is now the way that things
should operate.
Our own requirement was a need to install some programs. Would it
be possible to have one/several accounts available for 'hire' in
the same way that testinstall is, but with more limited privilages
sufficient to do things like this ?
Keith
|
| 218.2 | General privileged accounts | INCH::GARLAND | Howard GARLAND @UCG, 781-4323 | Thu Mar 02 1989 09:30 | 16 |
| I will add my support to the final paragraph of the last note.
i.e. Since we will need privileged accounts for activities other
than VMSINSTAL, how about the following accounts existing:
TESTINSTALL - for doing VMSINSTALs, all privileges.
PRIVILEGED1 - for doing everything else other than VMSINSTAL,
all privileges.
PRIVILEGED2 - as above
PRIVILEGED3 - as above
How about it?
Howard
|
| 218.3 | A stickler for accuracy - if nothing else! | GROYNE::HAYES | Ian Hayes, DTN 781 ext 4327 | Mon Mar 20 1989 13:42 | 22 |
| TIME OUT
I know I'm being picky and it isn't relevant to the subject of this
topic, but...
RE: .0
> VMSINSTAL creates system wide logicals and symbols. If a second
>version were to be invoked at the same time the two processes would
>interfere with each others logicals and/or symbols.
There is no such thing as a system wide symbol. All symbols are
process-private. If I remember correctly, the main reason that
VMSINSTAL trips itself up if it is run more than once at a time
is because it uses temporary files with a fixed name. Hence when
the first invocation of VMSINSTAL deletes them, the second gets
upset because the file it expected to find ain't there no more!
It also gets a bit hairy if two VMSINSTALs try to update the DCL
tables or the help library at the same time.
Now, back to work.
Ian.
|