View Issue Details

IDProjectCategoryView StatusLast Update
00006511003.1(2008)/Issue 7System Interfacespublic2019-06-10 08:55
Reportergeoffclare Assigned Toajosey  
PrioritynormalSeverityObjectionTypeError
Status ClosedResolutionAccepted 
NameGeoff Clare
OrganizationThe Open Group
User Reference
Sectionfpathconf
Page Number888, 889
Line Number29550-29551, 29612
Interp StatusApproved
Final Accepted TextSee 0000651:0001481.
Summary0000651: ELOOP for pathconf() should be "may fail"
DescriptionThe fpathconf() page has a "shall fail" ELOOP error for pathconf() that
should be in the "may fail" part of the ERRORS section.

Also, the paragraph in the RATIONALE that explains why most [f]pathconf()
errors are optional needs updating to account for [EOVERFLOW].
Desired ActionMove the ELOOP "shall fail" error at page 888 line 29550-29551 to
the "may fail" part of the ERRORS section before the other ELOOP
error at line 29558.

At page 889 line 29612 change:

    ... not required to detect any of the errors except the meaning of
    [EINVAL] that indicates that the value of name is not valid for
    that variable.

to:

    ... not required to detect any of the errors except the meaning of
    [EINVAL] that indicates that the value of name is not valid for
    that variable, and the [EOVERFLOW] error that indicates the value
    to be returned is larger than {LONG_MAX}.
Tagstc2-2008

Activities

Don Cragun

2013-02-28 17:14

viewer   bugnote:0001481

The standard states that an ELOOP error is required in this case, and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor.

Rationale:
-------------
This is inconsistent with other parts of the standard for similar cases.

Notes to the Editor (not part of this interpretation):
-------------------------------------------------------
Make the changes suggested in the Desired Action.

ajosey

2013-03-29 08:04

manager   bugnote:0001514

Interpretation Proposed 29 Mar 2013

ajosey

2013-05-03 12:20

manager   bugnote:0001582

Interpretation approved 3 May 2013

Issue History

Date Modified Username Field Change
2013-02-06 11:42 geoffclare New Issue
2013-02-06 11:42 geoffclare Status New => Under Review
2013-02-06 11:42 geoffclare Assigned To => ajosey
2013-02-06 11:42 geoffclare Name => Geoff Clare
2013-02-06 11:42 geoffclare Organization => The Open Group
2013-02-06 11:42 geoffclare Section => fpathconf
2013-02-06 11:42 geoffclare Page Number => 888, 889
2013-02-06 11:42 geoffclare Line Number => 29550-29551, 29612
2013-02-06 11:42 geoffclare Interp Status => ---
2013-02-07 14:11 geoffclare Desired Action Updated
2013-02-28 17:14 Don Cragun Note Added: 0001481
2013-02-28 17:14 Don Cragun Status Under Review => Interpretation Required
2013-02-28 17:14 Don Cragun Resolution Open => Accepted
2013-02-28 17:15 Don Cragun Final Accepted Text => See 0000651:0001481.
2013-02-28 17:15 Don Cragun Tag Attached: tc2-2008
2013-02-28 17:16 Don Cragun Interp Status --- => Pending
2013-03-29 08:04 ajosey Interp Status Pending => Proposed
2013-03-29 08:04 ajosey Note Added: 0001514
2013-05-03 12:20 ajosey Interp Status Proposed => Approved
2013-05-03 12:20 ajosey Note Added: 0001582
2019-06-10 08:55 agadmin Status Interpretation Required => Closed