Message-ID: <03e001c30d29$b0d81fc0$0600000a@broadpark.no>
From: "Gisle Vanem" <giva AT bgnett DOT no>
To: <djgpp-workers AT delorie DOT com>
References:  <03b301c30d1e$3bd216f0$0600000a AT broadpark DOT no> <200304280105 DOT h3S15fDZ026158 AT envy DOT delorie DOT com>
Subject: Re: /dev/full not full afterall
Date: Mon, 28 Apr 2003 03:58:40 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Reply-To: djgpp-workers AT delorie DOT com

> > I find that in latest 2.04 alpha1, writing to /dev/full doesn't fail with ENOSPC
> > as the info-page says. Example program:
> 
> I'm inclined to think that the stdio buffering is getting in the way.
> Have you tried unbuffered?  Have you checked the return value of the
> fclose() call (that's when the data is written out)?
 
Spot on, with _IONBF on:
  fprintf: No space left on drive (ENOSPC)
  -1 bytes to /dev/full, errno 26

--gv