Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!husc6!mit-eddie!genrad!decvax!ucbvax!ULKYVX.BITNET!SYSMSH
From: SYSMSH@ULKYVX.BITNET
Newsgroups: comp.os.vms
Subject: re: DECserver query
Message-ID: <8706160826.AA00126@ucbvax.Berkeley.EDU>
Date: Sun, 14-Jun-87 14:13:00 EDT
Article-I.D.: ucbvax.8706160826.AA00126
Posted: Sun Jun 14 14:13:00 1987
Date-Received: Sun, 21-Jun-87 06:06:13 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: University of Louisville
Lines: 27

>   We are thinking about getting DECservers (yes, I've queried
>this one before, but not this aspect).  We also have a GANDALF
>PACX, so the 200's are needed for modem control.  I've looked at
>the User Guide, and frankly, the user can do too much to "his"
>port, and leave it around for the next unsuspecting connection.
>   I'd like to limit (or inhibit entirely) the following "user"
>functionality:  LOCK, SET/DEFINE PORT PARITY/FLOW/CHARACTER,
>and perhaps others, since it appears that these could get left
>around.

We've got several DECserver-200's connected to a terminal switch.  Modem
control is enabled.  I ran into the same problems with the DEFINE and
LOCK commands.  Users were able to alter the permanent characteristics
of any random port.  LOCK would also not clear out if the line was
dropped from the switch.  I was forced to disable LOCK and patch out
the DEFINE command in the PR801ENG.SYS file.  Thats about your only
option other than an SPR.  If you are interested in the technique
drop me a mail msg.  I allow the users to do SET commands because they
do clear out after the line drops.

Someday I'll submit an SPR for making DEFINE PORT an optionally privileged
command and making a LOCKED port unlock upon line drop.

Mark Hittinger/systems programmer iv/ocis south center
University of Louisville, Louisville, Ky 40292
sysmsh@ulkyvx.bitnet
sysmsh%ulkyvx.bitnet@wiscvm.wisc.edu