HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

Writting all login request to a file

 
SOLVED
Go to solution
Art Dantonio
Occasional Contributor

Writting all login request to a file

Need to keep a log of all logins not just unsuccessful attempts. Would like to write them to a file.
11 REPLIES
Ian Miller.
Honored Contributor
Solution

Re: Writting all login request to a file

use auditing
SET AUDIT/AUDIT/ENABLE=LOGIN=INTERACTIVE

(this will record all interactive logins. You can select more if you wish e.g BATCH, SUBPROCESS, NETWORK etc)

then use
ANAL/AUDIT to generate reports.
____________________
Purely Personal Opinion
Martin P.J. Zinser
Honored Contributor

Re: Writting all login request to a file

Hi,

Ian's approach is the clean solution. If you insist to do your own, you could instrument sylogin.com to capture this information.

Greetings, Martin
Antoniov.
Honored Contributor

Re: Writting all login request to a file

Hi,
Ian posted right.
If you will see succesfull entries you can use account command too.

@Antoniov
Antonio Maria Vigliotti
Jan van den Ende
Honored Contributor

Re: Writting all login request to a file

And one step further:
from the accounting info we extract session durations to produce management info.
Why they need it I don't know, but they were really enthousiastic when we were able to satisfy their request. I don't even know if they still use them, but WE do every once in a while if some questions come up.
It really shocks them if you can produce that kind of statistic from over a year ago!


hth


Jan
Don't rust yours pelled jacker to fine doll missed aches.
Ian Miller.
Honored Contributor

Re: Writting all login request to a file

You can monitor logouts too
SET AUDIT/AUDIT/ENABLE=LOGOUT=INTERACTIVE
then generate reports.

Although I find accounting best for the reports (when do people generally login, logout, how long do they stay connected etc) that management seem to find interesting.
____________________
Purely Personal Opinion
Art Dantonio
Occasional Contributor

Re: Writting all login request to a file

The system does not accept the word interactive.
v7.3.
Ian Miller.
Honored Contributor

Re: Writting all login request to a file

Slight mistoke. See
HELP SET AUDIT /ENABLE

/ENABLE=LOGIN=(keyword,...)

ALL BATCH
DETACHED DIALUP
LOCAL NETWORK
REMOTE SUBPROCESS
____________________
Purely Personal Opinion
Antoniov.
Honored Contributor

Re: Writting all login request to a file

I think Ian would post
SET AUDIT/AUDIT/ENABLE=LOGOUT=LOCAL

@Antoniov
Antonio Maria Vigliotti
Ian Miller.
Honored Contributor

Re: Writting all login request to a file

not many local login/logout nowadays. Mostly network
____________________
Purely Personal Opinion
Wim Van den Wyngaert
Honored Contributor

Re: Writting all login request to a file

You will get an alarm for every invalid password. Therefore, I set audit as

Breakin: dialup, local,remote,network, detached,server
Logfailure: batch,dialup,network, subprocess,detached

This gives users the oportunity to make interactive mistakes. Only interactive breakins (e.g. 5 invalid passwords) will be reported.
Wim
Ian Miller.
Honored Contributor

Re: Writting all login request to a file

auditing login failures is seperate from auditing logins. To record all interactive logins
SET AUDIT/AUDIT/ENABLE=LOGINS=(ALL, NOBATCH, NOSUBPROC,NODET)
____________________
Purely Personal Opinion