Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ames!nrl-cmf!mailrus!tut.cis.ohio-state.edu!bloom-beacon!athena.mit.edu!eichin
From: eichin@athena.mit.edu (Mark W. Eichin)
Newsgroups: comp.unix.aux
Subject: Re: fprintf() weirdness?
Keywords: portability fprintf core
Message-ID: <8474@bloom-beacon.MIT.EDU>
Date: 15 Dec 88 18:45:53 GMT
References: <8457@bloom-beacon.MIT.EDU> <347@cwjcc.CWRU.Edu>
Sender: daemon@bloom-beacon.MIT.EDU
Reply-To: eichin@athena.mit.edu (Mark W. Eichin)
Organization: Massachusetts Institute of Technology
Lines: 12

=Me
=where f=fdopen(s, "r") earlier (and is not NULL...) The catch: If I
>>chet@cwjcc.CWRU.EDU
>>Well, you could try opening the file for writing (unless that was just a 
>>typo above), with an fdopen(s,"r+") or fdopen(s,"w").  I don't know why the

Oops, typo. Actually, `s' was a socket() and it was then fdopen()ed
for "r" and "w", and the fprintf is going to the one opened for write.
Sorry for the confusion.

				Mark Eichin
			<eichin@athena.mit.edu>
		SIPB Member & Project Athena ``Watchmaker''