<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: net$server.log generation in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/net-server-log-generation/m-p/5174376#M26483</link>
    <description>Ravi,&lt;BR /&gt;&lt;BR /&gt;  Failure to create a log file is not considered fatal, and, obviously, can't be logged anywhere.&lt;BR /&gt;&lt;BR /&gt;  One way to block creation of new NET$SERVER.LOG files is to create one with version 32767&lt;BR /&gt;&lt;BR /&gt;$ CREATE SYS$LOGIN:NET$SERVER.LOG;32767&lt;BR /&gt;&lt;BR /&gt;  Another possibility is the target account lacks write access to it's SYS$LOGIN directory, or delete access to an existing NET$SERVER.LOG. &lt;BR /&gt;&lt;BR /&gt;  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.&lt;BR /&gt;&lt;BR /&gt;  To track where the files should be created,   enable login alarms and watch where the processes are being logged in:&lt;BR /&gt;&lt;BR /&gt;$ REPLY/ENABLE=SECURITY&lt;BR /&gt;$ SET AUDIT/ALARM/ENABLE=LOGIN=ALL</description>
    <pubDate>Mon, 11 May 2009 21:34:32 GMT</pubDate>
    <dc:creator>John Gillings</dc:creator>
    <dc:date>2009-05-11T21:34:32Z</dc:date>
    <item>
      <title>net$server.log generation</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/net-server-log-generation/m-p/5174373#M26480</link>
      <description>when does a net$server.log file will be generated. &lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;What does that file signifies?&lt;BR /&gt;Will it be generated on all environments or any exemptions?&lt;BR /&gt;&lt;BR /&gt;Many thanks&lt;BR /&gt;Ravi</description>
      <pubDate>Mon, 11 May 2009 11:10:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/net-server-log-generation/m-p/5174373#M26480</guid>
      <dc:creator>RAVIKANTH_3</dc:creator>
      <dc:date>2009-05-11T11:10:59Z</dc:date>
    </item>
    <item>
      <title>Re: net$server.log generation</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/net-server-log-generation/m-p/5174374#M26481</link>
      <description>Ravi,&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Mon, 11 May 2009 11:18:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/net-server-log-generation/m-p/5174374#M26481</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2009-05-11T11:18:05Z</dc:date>
    </item>
    <item>
      <title>Re: net$server.log generation</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/net-server-log-generation/m-p/5174375#M26482</link>
      <description>it could be that someone changed sys$system:net$server.com and modified the name of the log file. Or the directory.&lt;BR /&gt;&lt;BR /&gt;Or the T2T reused a process of a just finished T2T (thus append to the file will be done).&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Mon, 11 May 2009 11:35:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/net-server-log-generation/m-p/5174375#M26482</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2009-05-11T11:35:32Z</dc:date>
    </item>
    <item>
      <title>Re: net$server.log generation</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/net-server-log-generation/m-p/5174376#M26483</link>
      <description>Ravi,&lt;BR /&gt;&lt;BR /&gt;  Failure to create a log file is not considered fatal, and, obviously, can't be logged anywhere.&lt;BR /&gt;&lt;BR /&gt;  One way to block creation of new NET$SERVER.LOG files is to create one with version 32767&lt;BR /&gt;&lt;BR /&gt;$ CREATE SYS$LOGIN:NET$SERVER.LOG;32767&lt;BR /&gt;&lt;BR /&gt;  Another possibility is the target account lacks write access to it's SYS$LOGIN directory, or delete access to an existing NET$SERVER.LOG. &lt;BR /&gt;&lt;BR /&gt;  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.&lt;BR /&gt;&lt;BR /&gt;  To track where the files should be created,   enable login alarms and watch where the processes are being logged in:&lt;BR /&gt;&lt;BR /&gt;$ REPLY/ENABLE=SECURITY&lt;BR /&gt;$ SET AUDIT/ALARM/ENABLE=LOGIN=ALL</description>
      <pubDate>Mon, 11 May 2009 21:34:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/net-server-log-generation/m-p/5174376#M26483</guid>
      <dc:creator>John Gillings</dc:creator>
      <dc:date>2009-05-11T21:34:32Z</dc:date>
    </item>
    <item>
      <title>Re: net$server.log generation</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/net-server-log-generation/m-p/5174377#M26484</link>
      <description>Here is a web search command that can be useful for these questions:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.google.com/search?hl=en&amp;amp;q=net%24server.log+site%3Ah71000.www7.hp.com" target="_blank"&gt;http://www.google.com/search?hl=en&amp;amp;q=net%24server.log+site%3Ah71000.www7.hp.com&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;</description>
      <pubDate>Mon, 11 May 2009 22:29:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/net-server-log-generation/m-p/5174377#M26484</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2009-05-11T22:29:11Z</dc:date>
    </item>
    <item>
      <title>Re: net$server.log generation</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/net-server-log-generation/m-p/5174378#M26485</link>
      <description>becuase the log file generation is 32767, it is not generating any new files and it is blocking the new files generation.&lt;BR /&gt;So i have deleted this generation and logs got generated.</description>
      <pubDate>Fri, 15 May 2009 13:51:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/net-server-log-generation/m-p/5174378#M26485</guid>
      <dc:creator>RAVIKANTH_3</dc:creator>
      <dc:date>2009-05-15T13:51:47Z</dc:date>
    </item>
  </channel>
</rss>

