home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!usc!elroy.jpl.nasa.gov!news.claremont.edu!nntp-server.caltech.edu!SOL1.GPS.CALTECH.EDU!CARL
- From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
- Newsgroups: comp.os.vms
- Subject: Re: TT_AccPorNam field remains null on a SHOW USERS output ?
- Date: 30 Dec 1992 12:06:16 GMT
- Organization: HST Wide Field/Planetary Camera
- Lines: 26
- Distribution: world
- Message-ID: <1hs3boINNnqs@gap.caltech.edu>
- References: <01GSVSPU15CY006MJF@VAXF.COLORADO.EDU>
- Reply-To: carl@SOL1.GPS.CALTECH.EDU
- NNTP-Posting-Host: sol1.gps.caltech.edu
-
- In article <01GSVSPU15CY006MJF@VAXF.COLORADO.EDU>, DWING@UH01.Colorado.EDU (Dan Wing) writes:
- >... Somewhat related to this, it shore would be 'cool' if DEC could include
- >this same information for the FTAnn: devices for X terminals. Ah, well,
- >maybe next version?
-
- A related wish is: I'd like DEC to allow system managers the option of having
- LOGINOUT write a record to the accounting file at the time of login which would
- specify the port name, the access port name, and the virtual terminal
- associated with the login. Here's where I'm coming from:
- A user logs in via some terminal that uses a terminal driver that
- allows the use of virtual terminals;
- The user DISCONNECTs
- The user logs in again (possibly from a different terminal) and
- CONNECTs to his DISCONNECTed job;
- Now for the $64 question: In looking at the accounting file, how do you
- determine where the user is coming from? Yeah, I know, there's probably some
- way to get the AUDIT mechanisms to record this information, but I'd rather have
- it show up in ACCOUNTNG.DAT.
- --------------------------------------------------------------------------------
- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL
-
- Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My
- understanding of astronomy is purely at the amateur level (or below). So
- unless what I'm saying is directly related to VAX/VMS, don't hold me or my
- organization responsible for it. If it IS related to VAX/VMS, you can try to
- hold me responsible for it, but my organization had nothing to do with it.
-