- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Ideas needed for capturing User login data from sy...
Operating System - OpenVMS
1758743
Members
2691
Online
108874
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2007 09:33 PM
04-15-2007 09:33 PM
Re: Ideas needed for capturing User login data from sys$sylogin.
Thomas,
As John noted, the Accounting file is not written till the end of the session. As was also noted, the AUDIT log is written as events happen. An AUDIT listener is only needed in the event that is necessary to process events in real time, if they are merely to be examined later, the audit journal is sufficient.
There is no need for a shared file in this case, and indeed, if this data is being captured for some form of audit requirement, there is a STRONG reason that the file should not be a shared file writeable by all. The Audit log would fit the bill quite handsomely.
- Bob Gezelter, http://www.rlgsc.com
As John noted, the Accounting file is not written till the end of the session. As was also noted, the AUDIT log is written as events happen. An AUDIT listener is only needed in the event that is necessary to process events in real time, if they are merely to be examined later, the audit journal is sufficient.
There is no need for a shared file in this case, and indeed, if this data is being captured for some form of audit requirement, there is a STRONG reason that the file should not be a shared file writeable by all. The Audit log would fit the bill quite handsomely.
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2007 09:59 PM
04-16-2007 09:59 PM
Re: Ideas needed for capturing User login data from sys$sylogin.
Depending on the sensitivity/size of the data, why not just log it to OPERATOR.LOG and extract it using a script?
REQUEST/TO=CENTRAL|OPERn "Your message"
REQUEST/TO=CENTRAL|OPERn "Your message"
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP