Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!lll-tis!ptsfa!ihnp4!homxb!hou2d!jmprice
From: jmprice@hou2d.UUCP (J.PRICE)
Newsgroups: comp.os.vms
Subject: Re: VMS C SYS$OUTPUT
Message-ID: <1568@hou2d.UUCP>
Date: Mon, 14-Sep-87 09:20:07 EDT
Article-I.D.: hou2d.1568
Posted: Mon Sep 14 09:20:07 1987
Date-Received: Tue, 15-Sep-87 06:32:33 EDT
References: <870912025526.02e@CitHex.Caltech.Edu>
Organization: AT&T Bell Laboratories, Holmdel
Lines: 14
Summary: Maybe you could try....

In article <870912025526.02e@CitHex.Caltech.Edu>, carl@CITHEX.CALTECH.EDU (Carl J Lydick) writes:
> 
>> I have been using VAX C version 2.3 to write a program designed to be run
>> as a detached process.  It runs fine, but VAX C insists on opening
>> SYS$OUTPUT and SYS$ERROR even though the program does not do any output.
>> There are no Output functions used in the program and when I run it /detached
>> it creates files called SYS$OUTPUT. and SYS$ERROR.  Is there a way around
>> this? Is main() doing this? I can close the files with fclose(stdout) and
>> fclose(stderr) but that still leaves me with useless files in my directory.
> 
If you don't have some problem related to too many files open,  why don't
you just assign SYS$OUTPUT and SYS$ERROR to the NULL device.

John Price