Use of the information contained in this unapproved document is at your own risk.

Last update: 10 April,2001

                                                                1003.1-90 #72

 _____________________________________________________________________________

	Interpretation Number:	XXXX
	Topic:			write and EFBIG
	Relevant Sections:	6.4.2.4


Interpretation Request: (Defect Report)
-----------------------

	Date: Wed, 23 Aug 1995 14:47:34 -0500 (CDT)


This is a request for interpretation of IEEE standard 1003.1-1990 (ISO
9945-1:1990)

Interpetation Request:

In Section 6.4.2.4 [errno values returned from write()], there is an
entry for EFBIG (lines 275-276, page 121):

	An attempt was made to write a file that exceeds an
	implementation-defined maximum file size.

The question regards the phrase "maximum file size". Does this phrase
refer to the "maximum size that a file can possibly or theoretically
become on the given implementation" or can it also mean such things as
"maximum file size allowed to this process by the implementation"?

On many operating systems, a per-process file size limit can be set. Is
it conforming for the implementation to set EFBIG when a process'
write() hits this limit?

It appears to me that this would be conforming behavior, since this also
is an "implementation-defined maximum file size", for that process.

 
IEEE Interpretation for 1003.1-1990 (1003.1-90 #72)
-----------------------------------
The standard clearly states the requirements for write() and the EFBIG
error and permits this behavior so long as this limit
is described in the accompanying conformance documentation.

Rationale for Interpretation:
-----------------------------
None.

Forwarded to Interpretation group: Aug 29 1995
Resolution forwarded for review: Oct 18 1995
Finalised: Nov 21 1995