📄 xbd_chap02.html
字号:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta name="generator" content="HTML Tidy, see www.w3.org"><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"><link type="text/css" rel="stylesheet" href="style.css"><!-- Generated by The Open Group's rhtm tool v1.2.1 --><!-- Copyright (c) 2001-2003 The Open Group, All Rights Reserved --><title>Conformance</title></head><body bgcolor="white"><script type="text/javascript" language="JavaScript" src="../jscript/codes.js"></script><basefont size="3"> <!--header start--><center><font size="2">The Open Group Base Specifications Issue 6<br>IEEE Std 1003.1, 2003 Edition<br>Copyright © 2001-2003 The IEEE and The Open Group, All Rights reserved.</font></center><!--header end--><hr size="2" noshade><h2><a name="tag_02"></a>Conformance</h2><h3><a name="tag_02_01"></a>Implementation Conformance</h3><h4><a name="tag_02_01_01"></a>Requirements</h4><p>A <i>conforming implementation</i> shall meet all of the following criteria:</p><ol><li><p>The system shall support all utilities, functions, and facilities defined within IEEE Std 1003.1-2001 that arerequired for POSIX conformance (see <a href="#tag_02_01_03">POSIX Conformance</a> ). These interfaces shall support the functionalbehavior described herein.</p></li><li><p>The system may support one or more options as described under <a href="#tag_02_01_05">Option Groups</a> . When an implementationclaims that an option is supported, all of its constituent parts shall be provided.</p></li><li><p>The system may support the X/Open System Interface Extension (XSI) as described under <a href="#tag_02_01_04">XSIConformance</a> .</p></li><li><p>The system may provide additional utilities, functions, or facilities not required by IEEE Std 1003.1-2001.Non-standard extensions of the utilities, functions, or facilities specified in IEEE Std 1003.1-2001 should be identifiedas such in the system documentation. Non-standard extensions, when used, may change the behavior of utilities, functions, orfacilities defined by IEEE Std 1003.1-2001. The conformance document shall define an environment in which an applicationcan be run with the behavior specified by IEEE Std 1003.1-2001. In no case shall such an environment require modificationof a Strictly Conforming POSIX Application (see <a href="#tag_02_02_01">Strictly Conforming POSIX Application</a> ).</p></li></ol><h4><a name="tag_02_01_02"></a>Documentation</h4><p>A conformance document with the following information shall be available for an implementation claiming conformance toIEEE Std 1003.1-2001. The conformance document shall have the same structure as IEEE Std 1003.1-2001, with theinformation presented in the appropriate sections and subsections. Sections and subsections that consist solely of subordinatesection titles, with no other information, are not required. The conformance document shall not contain information about extendedfacilities or capabilities outside the scope of IEEE Std 1003.1-2001.</p><p>The conformance document shall contain a statement that indicates the full name, number, and date of the standard that applies.The conformance document may also list international software standards that are available for use by a Conforming POSIXApplication. Applicable characteristics where documentation is required by one of these standards, or by standards of governmentbodies, may also be included.</p><p>The conformance document shall describe the limit values found in the headers <a href="limits.h.html"><i><limits.h></i></a> and <a href="unistd.h.html"><i><unistd.h></i></a> , stating values, theconditions under which those values may change, and the limits of such variations, if any.</p><p>The conformance document shall describe the behavior of the implementation for all implementation-defined features defined inIEEE Std 1003.1-2001. This requirement shall be met by listing these features and providing either a specific referenceto the system documentation or providing full syntax and semantics of these features. When the value or behavior in theimplementation is designed to be variable or customized on each instantiation of the system, the implementation provider shalldocument the nature and permissible ranges of this variation.</p><p>The conformance document may specify the behavior of the implementation for those features where IEEE Std 1003.1-2001states that implementations may vary or where features are identified as undefined or unspecified.</p><p>The conformance document shall not contain documentation other than that specified in the preceding paragraphs except where suchdocumentation is specifically allowed or required by other provisions of IEEE Std 1003.1-2001.</p><p>The phrases "shall document" or "shall be documented" in IEEE Std 1003.1-2001 mean that documentation of thefeature shall appear in the conformance document, as described previously, unless there is an explicit reference in the conformancedocument to show where the information can be found in the system documentation.</p><p>The system documentation should also contain the information found in the conformance document.</p><h4><a name="tag_02_01_03"></a>POSIX Conformance</h4><p>A conforming implementation shall meet the following criteria for POSIX conformance.</p><h5><a name="tag_02_01_03_01"></a>POSIX System Interfaces</h5><ul><li><p>The system shall support all the mandatory functions and headers defined in IEEE Std 1003.1-2001, and shall set thesymbolic constant _POSIX_VERSION to the value 200112L.</p></li><li><p>Although all implementations conforming to IEEE Std 1003.1-2001 support all the features described below, there may besystem-dependent or file system-dependent configuration procedures that can remove or modify any or all of these features. Suchconfigurations should not be made if strict compliance is required.</p><p>The following symbolic constants shall either be undefined or defined with a value other than -1. If a constant is undefined, anapplication should use the <a href="../functions/sysconf.html"><i>sysconf</i>()</a>, <a href="../functions/pathconf.html"><i>pathconf</i>()</a>, or <a href="../functions/fpathconf.html"><i>fpathconf</i>()</a> functions, orthe <a href="../utilities/getconf.html"><i>getconf</i></a> utility, to determine which features are present on the system at thattime or for the particular pathname in question.</p><ul><li><p>_POSIX_CHOWN_RESTRICTED</p><p>The use of <a href="../functions/chown.html"><i>chown</i>()</a> is restricted to a process with appropriate privileges, and tochanging the group ID of a file only to the effective group ID of the process or to one of its supplementary group IDs.</p></li><li><p>_POSIX_NO_TRUNC</p><p>Pathname components longer than {NAME_MAX} generate an error.</p></li></ul></li><li><p>The following symbolic constants shall be defined as follows:</p><ul><li><p>_POSIX_JOB_CONTROL shall have a value greater than zero.</p></li><li><p>_POSIX_SAVED_IDS shall have a value greater than zero.</p></li><li><p>_POSIX_VDISABLE shall have a value other than -1.</p></li></ul><basefont size="2"> <dl><dt><b>Note:</b></dt><dd>The symbols above represent historical options that are no longer allowed as options, but are retained here forbackwards-compatibility of applications.</dd></dl><basefont size="3"></li><li><p>The system may support one or more options (see <a href="#tag_02_01_06">Options</a> ) denoted by the following symbolicconstants:</p><ul><li><p>_POSIX_ADVISORY_INFO</p></li><li><p>_POSIX_ASYNCHRONOUS_IO</p></li><li><p>_POSIX_BARRIERS</p></li><li><p>_POSIX_CLOCK_SELECTION</p></li><li><p>_POSIX_CPUTIME</p></li><li><p>_POSIX_FSYNC</p></li><li><p>_POSIX_IPV6</p></li><li><p>_POSIX_MAPPED_FILES</p></li><li><p>_POSIX_MEMLOCK</p></li><li><p>_POSIX_MEMLOCK_RANGE</p></li><li><p>_POSIX_MEMORY_PROTECTION</p></li><li><p>_POSIX_MESSAGE_PASSING</p></li><li><p>_POSIX_MONOTONIC_CLOCK</p></li><li><p>_POSIX_PRIORITIZED_IO</p></li><li><p>_POSIX_PRIORITY_SCHEDULING</p></li><li><p>_POSIX_RAW_SOCKETS</p></li><li><p>_POSIX_REALTIME_SIGNALS</p></li><li><p>_POSIX_SEMAPHORES</p></li><li><p>_POSIX_SHARED_MEMORY_OBJECTS</p></li><li><p>_POSIX_SPAWN</p></li><li><p>_POSIX_SPIN_LOCKS</p></li><li><p>_POSIX_SPORADIC_SERVER</p></li><li><p>_POSIX_SYNCHRONIZED_IO</p></li><li><p>_POSIX_THREAD_ATTR_STACKADDR</p></li><li><p>_POSIX_THREAD_CPUTIME</p></li><li><p>_POSIX_THREAD_ATTR_STACKSIZE</p></li><li><p>_POSIX_THREAD_PRIO_INHERIT</p></li><li><p>_POSIX_THREAD_PRIO_PROTECT</p></li><li><p>_POSIX_THREAD_PRIORITY_SCHEDULING</p></li><li><p>_POSIX_THREAD_PROCESS_SHARED</p></li><li><p>_POSIX_THREAD_SAFE_FUNCTIONS</p></li><li><p>_POSIX_THREAD_SPORADIC_SERVER</p></li><li><p>_POSIX_THREADS</p></li><li><p>_POSIX_TIMEOUTS</p></li><li><p>_POSIX_TIMERS</p></li><li><p>_POSIX_TRACE</p></li><li><p>_POSIX_TRACE_EVENT_FILTER</p></li><li><p>_POSIX_TRACE_INHERIT</p></li><li><p>_POSIX_TRACE_LOG</p></li><li><p>_POSIX_TYPED_MEMORY_OBJECTS</p></li></ul><p>If any of the symbolic constants _POSIX_TRACE_EVENT_FILTER, _POSIX_TRACE_LOG, or _POSIX_TRACE_INHERIT is defined to have a valueother than -1, then the symbolic constant _POSIX_TRACE shall also be defined to have a value other than -1.</p></li><li><p><sup>[<a href="javascript:open_code('XSI')">XSI</a>]</sup> <img src="../images/opt-start.gif" alt="[Option Start]" border="0">The system may support the XSI extensions (see <a href="#tag_02_01_05_02">XSI Option Groups</a> ) denoted by the following symbolicconstants:</p><ul><li><p>_XOPEN_CRYPT</p></li><li><p>_XOPEN_LEGACY</p></li><li><p>_XOPEN_REALTIME</p></li><li><p>_XOPEN_REALTIME_THREADS</p></li><li><p>_XOPEN_UNIX <img src="../images/opt-end.gif" alt="[Option End]" border="0"></p></li></ul></li></ul><h5><a name="tag_02_01_03_02"></a>POSIX Shell and Utilities</h5><ul><li><p>The system shall provide all the mandatory utilities in the Shell and Utilities volume of IEEE Std 1003.1-2001 withall the functional behavior described therein.</p></li><li><p>The system shall support the Large File capabilities described in the Shell and Utilities volume ofIEEE Std 1003.1-2001.</p></li><li><p>The system may support one or more options (see <a href="#tag_02_01_06">Options</a> ) denoted by the following symbolicconstants. (The literal names below apply to the <a href="../utilities/getconf.html"><i>getconf</i></a> utility.)</p><ul><li><p>POSIX2_C_DEV</p></li>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -