home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!gatech!usenet.ins.cwru.edu!agate!ucbvax!NSCVAX.PRINCETON.EDU!dragon
- From: dragon@NSCVAX.PRINCETON.EDU (Mighty Firebreather)
- Newsgroups: comp.os.vms
- Subject: Re: TT_AccPorNam field remains null on a SHOW USERS output ?
- Message-ID: <00965CE9.1CCC8820.31019@nscvax.princeton.edu>
- Date: 29 Dec 92 15:04:38 GMT
- Sender: daemon@ucbvax.BERKELEY.EDU
- Distribution: world
- Organization: The Internet
- Lines: 43
-
-
- Ehud Gavron <gavron@vesta.sunquest.com> writes:
- >
- >In article <1992Dec27.233720.1@woods.ulowell.edu>, sabotkap@woods.ulowell.edu writes...
-
- <much stuff omitted>
-
- > SET TERM/INQ
- >in SYLOGIN is a reason for you to be shot, by the way...
- >
-
- Ehud,
-
- I know that SET TERM /INQ can cause problems in some circumstances,
- most notably under DECWindows but this reaction seems a little extreme.
-
- I have the following in my SYS$SYLOGIN:
-
- $ IF F$MODE() .NES. "INTERACTIVE" THEN GOTO DEFINE
- $! We know what's connected to the TX ports. If terminal is not on one of
- $! the multiplexers, find out what it is.
- $!
- $ IF F$EXTRACT(1, 2, F$GETDVI("TT", "DEVNAM")) .EQS. "TX" THEN GOTO 10$
- $ SET TERMINAL /INQUIRE
- $10$:
- $! If the login is via a modem, we need to ask what it is anyway.
- $!
- $ IF F$GETDVI("TT", "TT_MODEM") THEN $ SET TERMINAL /INQUIRE
-
- Given that a number of important utilities like to know what sort
- of terminal they are talking to and that, in many cases; e.g. terminal
- servers, you don't know unless you ask, why should one not use SET
- TERMINAL /INQUIRE?
-
-
- *************************************************************************
- * *
- * Here, there be dragons! *
- * dragon@nscvax.princeton.edu *
- * *
- * Richard B. Gilbert *
- *************************************************************************
-
-