Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: RE: generation of abundant sys$error and sys$output files
From: Mighty Firebreather <dragon@nscvax.princeton.edu>
Date: Thu, 15 Oct 1992 14:02:58 EDT
Reply-To: Mighty Firebreather <dragon@nscvax.princeton.edu>
Organization: The Internet
Return-Path: <SYNFUL@CMUTEK.CC.CMU.EDU>
Errors-To: SYNFUL@CMUTEK.CC.CMU.EDU
X-Listname: CMU-TEK TCP/IP Mailing list <CMU-TEK-TCP@CMUTEK.CC.CMU.EDU>
CC: cmu-tek-tcp@cmutek.cc.cmu.edu

	Bryan G. Peterson <PETERSON@PHYSC1.BYU.EDU> writes:
>
>I am currently running CMU-TEK TCP/IP 6.6-5 on VMS 5.5-1.  For a long time I
>have been getting a collection of files named SYS$OUTPUT. and SYS$ERROR. in
>SYS$MANAGER and SYS$SYSTEM.  These files seem to proliferate at an exteremly
>variable rate and the two most recent ones are generally currently open with
>the IPACP as the owner process.  The system with the most activity is now up
>to version 18000 (give or take a few) and over the weekend these things
>had proliferated to the point that it caused a header full error on the
>system disk.  It appears to me that this is a bug since these files are all
>completely empty (but they each still take up a header block).  Is there a
>way to shut off these files?  Or at least to slow down the rate of production?
>

	This is a question that has come up before.  I'm including a
message sent to the list almost two years ago.  I don't know if the
suggested solution will work or not; I've never tried it as I have never
had the problem to any significant degree.

>From:	"Bruce R. Miller" <bm17+@andrew.cmu.edu>  7-DEC-1990 20:54:22.44
>To:	CMU TEK <cmu-tek-tcp+@andrew.cmu.edu>,
>CC:
>Subj:	Re: sys$output. and sys$error.
>
>Date: Fri,  7 Dec 90 19:31:42 -0500 (EST)
>From: "Bruce R. Miller" <bm17+@andrew.cmu.edu>
>
>> Excerpts from internet.cmu-tek-tcp: 5-Dec-90 sys$output. and sys$error.
>> DON ROBERTS, PDQ VMS@bii (1094)
>
>> Using my CMU/TEK with DNS, I get a lot of SYS$OUTPUT.; and sys$error.;
>> files
>> created on my disks.  Bruce once told me that the way to get it to stop
>> doing
>> this was to put NL: (or some such) in my WKS lines in inet$config.  The
>> problem
>> is that I went through several debugging iterations that wiped out the
>> config
>> file that had these entries, and I (naturally) didn't record elsewhere
>> what and
>> where to put these.  My flawed memory doesn't recall, and Bruce, believe
>> it or
>> not, is uncommunicative when I have asked for a repeat of the fix.
>> Anyone else
>> dealt with this problem and could tell me the actual text and which
>> colons
>> between in my WKS lines?
>
>uncommunicative, yes.  willing, yes.  able, no, until now.
>
>I think what you want to do is define/sys TCP$NULL to be NLA0:
>put TCP$NULL into the WKS records in the appropriate fields
>as they are doumented by comments in INET$CONFIG.
>
>I made the fields default to SYS$OUTPUT/whatever and I didn't
>realize my mistake until later when Mark Berryman pointed this
>out.  I believe the defaults are now "NLA0:".
>
>-bruce r miller
> CMU NetDev

	I hope this is some help.


*************************************************************************
*                                                                       *
*                        Here, there be dragons!                        *
*                      dragon@nscvax.princeton.edu                      *
*                                                                       *
*                                                Richard B. Gilbert     *
*************************************************************************