Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!yetti!geac!daveb
From: daveb@geac.UUCP
Newsgroups: comp.lang.c
Subject: Re: stdio error detection
Message-ID: <1918@geac.UUCP>
Date: Thu, 3-Dec-87 08:08:18 EST
Article-I.D.: geac.1918
Posted: Thu Dec  3 08:08:18 1987
Date-Received: Sun, 6-Dec-87 11:38:28 EST
References: <289@cresswell.quintus.UUCP> <9022@utzoo.UUCP>
Reply-To: daveb@geac.UUCP (David Collier-Brown)
Organization: The little blue rock next to that twinkly star.
Lines: 20
Keywords: errno fclose fopen stdio errors

In article <9022@utzoo.UUCP> henry@utzoo.UUCP (Henry Spencer) writes:
>As others have mentioned, the buffer flush that often accompanies fclose()
>can produce an I/O error.  Not common.  However, checking for it is *vital*
>on systems with disk quotas, because that flush may blow the quota and fail.

  I might add that it is just plain good practice, on Unix or
whatever, whether or not you have disk quotas:
  1. Some machines are inherently small (desktop stuff),
  2. Some machines are run at close to 100% full (lots!), and
  3. Some machines suffer horrible faults at 100% full...

  David (Mr Reality) Haynes, the systems administrator here, noted
that we fall into class three (we've got a Berzerkly box).

--dave (oh my aching disk drive) c-b
-- 
 David Collier-Brown.                 {mnetor|yetti|utgpu}!geac!daveb
 Geac Computers International Inc.,   |  Computer Science loses its
 350 Steelcase Road,Markham, Ontario, |  memory (if not its mind)
 CANADA, L3R 1B3 (416) 475-0525 x3279 |  every 6 months.