Aardvark Summary Table ______________________ ERN 1 Accept ERN 2 Accept ERN 3 Accept ERN 4 Duplicate of 5 ERN 5 Accept as marked ERN 6 Duplicate of 5 ERN 7 Accept ERN 8 Accept ERN 9 Accept ERN 10 Accept ERN 11 Accept ERN 12 Accept ERN 13 Accept ERN 14 Accept ERN 15 Accept ERN 16 Accept ERN 17 Accept as marked ERN 18 Accept _____________________________________________________________________________ OBJECTION Enhancement Request Number 1 gwc:opengroup.org BUG in XSHd1 (rdvk# 3) [gwc XSH ERN 42] Mon, 17 Jul 2006 11:58:04 +0100 _____________________________________________________________________________ Accept_X___ Accept as marked below_____ Duplicate_____ Reject_____ Rationale for rejected or partial changes: _____________________________________________________________________________ Page: 58 Line: 2333 Section: 2.9.5.2 Problem: In the response to XSH ERN 42 it was agreed that there are inconsistencies in the standard related to use of sigpause() in threaded applications. Part of the solution was to mark the function obsolescent. However, the original problem remains, i.e. that the description of sigpause() says its use "is unspecified in a multi-threaded process" and yet it is required to contain a cancellation point. Action: Move sigpause() from the "shall" cancellation point list (line 2333) to the "may" list (line 2361). [Ed recommendation: Accept] _____________________________________________________________________________ OBJECTION Enhancement Request Number 2 gwc:opengroup.org BUG in XSHd1 (rdvk# 1) [gwc XBD ERN 4 - XSH] Mon, 17 Jul 2006 11:58:04 +0100 _____________________________________________________________________________ Accept_X___ Accept as marked below_____ Duplicate_____ Reject_____ Rationale for rejected or partial changes: _____________________________________________________________________________ Page: 104 Line: 3979 Section: accept Problem: The changes from XBD ERN 4 to EMFILE errors on individual function pages (which were not detailed in the original defect report) are incomplete. Austin/280r1 stated "in general EMFILE error descriptions change from {OPEN_MAX} file descriptors are currently open in the calling process. to: All file descriptors available to the process are currently open" but in one case the new text has been inserted before the old text rather than replacing it, and for several functions where the old text did not match the general case given in Austin/280r1 no change has been made where one is needed. Action: On page 104 line 3979 section accept delete: "{OPEN_MAX} file descriptors are currently open in the calling process". On page 279 line 9256 section dup change: "The number of file descriptors in use by this process would exceed {OPEN_MAX}." to: "All file descriptors available to the process are currently open." On page 345 line 11329 section fcntl change: "and {OPEN_MAX} file descriptors are currently open in the calling process, or" to: "and all file descriptors available to the process are currently open, or" On page 636 line 21057 section ioctl change: "The process has the maximum number of file descriptors currently open that it is allowed." to: "All file descriptors available to the process are currently open." On page 877 line 28710 section pipe change: "More than {OPEN_MAX} minus two file descriptors are already in use by this process." to: "All, or all but one, of the file descriptors available to the process are currently open." On page 989 line 31803 section posix_typed_mem_open change: "Too many file descriptors are currently in use by this process." to: "All file descriptors available to the process are currently open." On page 1356 line 42595 section shm_open change: "Too many file descriptors are currently in use by this process." to: "All file descriptors available to the process are currently open." On page 1423 line 44726 section socket change: "No more file descriptors are available for this process." to: "All file descriptors available to the process are currently open." On page 1425 line 44798 section socketpair change: "No more file descriptors are available for this process." to: "All file descriptors available to the process are currently open." [Ed recommendation: Accept] _____________________________________________________________________________ EDITORIAL Enhancement Request Number 3 gwc:opengroup.org BUG in XSHd1 (rdvk# 15) [gwc AI-044] Fri, 11 Aug 2006 15:20:31 +0100 _____________________________________________________________________________ Accept_X___ Accept as marked below_____ Duplicate_____ Reject_____ Rationale for rejected or partial changes: _____________________________________________________________________________ Page: 159 Line: 5572 Section: bind Problem: One of the changes identified in interpretation AI-044 has been applied incorrectly. The bind() ENOBUFS error was moved from the "may fail" section to the AF_UNIX-specific "shall fail" section instead of the generic "shall fail" section. Action: Move the bind() ENOBUFS error from line 5572 to after line 5556. [Ed recommendation: Accept] _____________________________________________________________________________ OBJECTION Enhancement Request Number 4 nick:usenix.org Bug in XSHd1 exit() (rdvk# 17) {NMS-exit-1} Thu, 31 Aug 2006 19:20:53 +0100 (BST) _____________________________________________________________________________ Accept_____ Accept as marked below_____ Duplicate_of_5 Reject_____ Rationale for rejected or partial changes: _____________________________________________________________________________ Page: 322 Line: 10569 Section: exit() Problem: The previous version of the standard required that all open streams be flushed (TC2 p XSH 313, line 10198). This version contains contradictory requirements at lines 10565 ("flush all open streams") and the following line, line 10569, which requires that "Open streams shall not be flushed". This will break many existing applications and all implementations. AI-085 also contains the requirement that the streams be flushed. I believe this change belongs only with the _exit()/_Exit() functions (where it is repeated, on page 89, line 3495). Action: Delete "Open streams shall not be flushed. Whether open streams are closed (without flushing) is implementation-defined." _____________________________________________________________________________ EDITORIAL Enhancement Request Number 5 gwc:opengroup.org BUG in XSHd1 (rdvk# 6) [gwc XSH ERN 128] Mon, 17 Jul 2006 11:58:04 +0100 _____________________________________________________________________________ Accept_____ Accept as marked below_X___ Duplicate_____ Reject_____ Rationale for rejected or partial changes: Page: 322 Line: 10569-10572 Section: exit Delete "Open streams shall not be flushed. Whether open streams are closed (without flushing) is implementation-defined." In XSH page 89 _exit add a new subheading Consequences of Process Termination Change exit() 10570: "Finally, control shall be terminated with the consequences described below. [CX] The exit() function shall terminate the calling process with the same consequences as per _exit().[/CX]" to: "Finally, the process shall be terminated [CX] with the same consequences as described for (see xref to _exit Consequence of Process Termination).[/CX]" CROSS VOL change to XBD signal.h page 308 line 10894 Change The process is terminated with all the consequences of _exit( ) except... To The process is terminated as if by a call to _exit( ) except... _____________________________________________________________________________ Page: 322 Line: 10569-10572 Section: exit Problem: Part of XSH ERN 128 (AI-085) intended only for _exit() and _Exit() has incorrectly been applied to exit() as well. Also, I would suggest some editorial cleanup of the last two sentences of the description. Action: Delete "Open streams shall not be flushed. Whether open streams are closed (without flushing) is implementation-defined." Change: "Finally, control shall be terminated with the consequences described below. [CX] The exit() function shall terminate the calling process with the same consequences as per _exit().[/CX]" to: "Finally, control shall be terminated [CX] with the same consequences as described for _Exit().[/CX]" _____________________________________________________________________________ COMMENT Enhancement Request Number 6 nick:usenix.org Bug in XSHd1 exit() (rdvk# 18) {NMS-exit-2} Thu, 31 Aug 2006 19:22:12 +0100 (BST) _____________________________________________________________________________ Accept_____ Accept as marked below_____ Duplicate_of_5 Reject_____ Rationale for rejected or partial changes: _____________________________________________________________________________ Page: 322 Line: 10572 Section: exit() Problem: "The exit() function shall terminate the calling process CX>with the same consequences as per _exit().with the same consequences as described for _exit() (see Consequences of Exit on page 89).