[1003.1(2008)/Issue 7 0000112]: ENOTSUP description in 2.3 does not match its uses

[Austin Group Bug Tracker <noreply@xxxxxxxxxxxxx>]

The following issue has been RESOLVED. 
====================================================================== 
http://austingroupbugs.net/view.php?id=112 
====================================================================== 
Reported By:                geoffclare
Assigned To:                ajosey
====================================================================== 
Project:                    1003.1(2008)/Issue 7
Issue ID:                   112
Category:                   System Interfaces
Type:                       Error
Severity:                   Objection
Priority:                   normal
Status:                     Resolved
Name:                       Geoff Clare 
Organization:               The Open Group 
User Reference:              
Section:                    2.3 
Page Number:                482 
Line Number:                16430 
Final Accepted Text:         
Resolution:                 Accepted
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-06-30 19:56 UTC
Last Modified:              2009-07-02 18:57 UTC
====================================================================== 
Summary:                    ENOTSUP description in 2.3 does not match its uses
Description: 
_____________________________________________________________________________
 OBJECTION                                        Enhancement Request
Number 41
 gwc:xxxxxxxxxxxxx                        Defect in XSH 2.3 ENOTSUP (rdvk#
 1)
 [gwc ENOTSUP desc]                             Tue, 9 Jun 2009 09:40:33
+0100

_____________________________________________________________________________

The general ENOTSUP description in 2.3 does not match its uses on
 individual function pages.  For example clock_nanosleep() uses
 it to indicate a clock ID is not supported; mmap() to indicate
 certain flags are not supported; mprotect() to indicate an
 access combination is not supported; and numerous pthread_*set*()
 functions use it to indicate that a requested value is not
 supported.

 Also most uses of ENOTSUP do not have XSI shading, so describing
 it in terms of an XSI feature group is wrong.

Desired Action: 
Change

     "The implementation does not support this feature of the Realtime
     Option Group."

 to

     "The implementation does not support the requested feature or
value."

======================================================================