- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: net$server.log generation
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
тАО05-11-2009 04:10 AM
тАО05-11-2009 04:10 AM
I have one decnet task to task communication. It is getting generated in one environment and not in other. When the box/node changes it is not getting generated.
What does that file signifies?
Will it be generated on all environments or any exemptions?
Many thanks
Ravi
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2009 04:18 AM
тАО05-11-2009 04:18 AM
Re: net$server.log generation
if a new NETWORK process is being created for an incoming DECnet-connection is under a specific username and that user's login-directory can be written to by the created process, a NET$SERVER.LOG file should be created.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2009 04:35 AM
тАО05-11-2009 04:35 AM
Re: net$server.log generation
Or the T2T reused a process of a just finished T2T (thus append to the file will be done).
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2009 02:34 PM
тАО05-11-2009 02:34 PM
SolutionFailure to create a log file is not considered fatal, and, obviously, can't be logged anywhere.
One way to block creation of new NET$SERVER.LOG files is to create one with version 32767
$ CREATE SYS$LOGIN:NET$SERVER.LOG;32767
Another possibility is the target account lacks write access to it's SYS$LOGIN directory, or delete access to an existing NET$SERVER.LOG.
By blocking log files you're potentially losing useful information. A better compromise to prevent disks being flooded is to set a version limit on the files.
To track where the files should be created, enable login alarms and watch where the processes are being logged in:
$ REPLY/ENABLE=SECURITY
$ SET AUDIT/ALARM/ENABLE=LOGIN=ALL
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2009 03:29 PM
тАО05-11-2009 03:29 PM
Re: net$server.log generation
http://www.google.com/search?hl=en&q=net%24server.log+site%3Ah71000.www7.hp.com
The Google "site:" keyword targets the search to the specified web server host, and the server listed above is the location of most OpenVMS information and documentation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-15-2009 06:51 AM
тАО05-15-2009 06:51 AM
Re: net$server.log generation
So i have deleted this generation and logs got generated.