Report 0561 Actions
Problem Report Number |
0561 |
Submitter's Classification |
Test Suite problem |
State |
Resolved |
Resolution |
Rejected (REJ) |
Problem Resolution ID |
REJ.X.0165 |
Raised |
1970-01-01 08:00 |
Updated |
2003-03-13 08:00 |
Published |
null |
Product Standard |
Commands and Utilities V3 (UNIX 98) |
Certification Program |
The Open Brand certification program |
Test Suite |
VSC version 5.0.1 |
Test Identification |
XOPEN.cmd/link 1034, 1038, 1039, 1040, 1041, 1043, 1046, 1047 |
Problem Summary |
PG4C.00113 This IR maintains that no error messages are required by the link command. |
Problem Text |
This Interpretation Request is for the following assertions: link 1034, 1038, 1039, 1040, 1041, 1043, 1046, 1047 These tests failed because output is expected on stderr when the exit status is >0. This is not an XPG5 requirement. Page 436 states: "STDERR Used only for diagnostic messages" Notice that this section makes no requirements for producing diagnostic messages, only where they will be directed to if produced. On Page 437 it states: "Exit Status The following exit values are returned: 0 Successful completion. >0 An error occurred." No requirement has been made here for diagnostic messages to be produced when exit status is >0.
|
Test Output |
*********************************************************************** /tset/XOPEN.cmd/link/link.ex 1 Failed Test Information: Assertion #1034 (A): "." wasn't found in standard error *********************************************************************** *********************************************************************** /tset/XOPEN.cmd/link/link.ex 1 Failed Test Information: Assertion #1038 (A): "." wasn't found in standard error *********************************************************************** *********************************************************************** /tset/XOPEN.cmd/link/link.ex 1 Failed Test Information: Assertion #1039 (A): "." wasn't found in standard error *********************************************************************** *********************************************************************** /tset/XOPEN.cmd/link/link.ex 1 Failed Test Information: Assertion #1040 (A): "." wasn't found in standard error "." wasn't found in standard error *********************************************************************** *********************************************************************** /tset/XOPEN.cmd/link/link.ex 1 Failed Test Information: Assertion #1041 (A): "." wasn't found in standard error *********************************************************************** *********************************************************************** /tset/XOPEN.cmd/link/link.ex 1 Failed Test Information: Assertion #1043 (A): "." wasn't found in standard error "." wasn't found in standard error *********************************************************************** *********************************************************************** /tset/XOPEN.cmd/link/link.ex 1 Failed Test Information: Assertion #1046 (C): "." wasn't found in standard error *********************************************************************** *********************************************************************** /tset/XOPEN.cmd/link/link.ex 1 Failed Test Information: Assertion #1047 (A): "." wasn't found in standard error ***********************************************************************
|
Review Information
Review Type |
TSMA Review |
Start Date |
null |
Completed |
null |
Status |
Complete |
Review Recommendation |
No Resolution Given |
Review Response |
Our opinion differs. Although the submitter is correct we believe that the specification clearly intended that users would be notified textually (rather than having to check the command's exit status) when the link command failed. We believe not stating this explicitly in the specification is an editorial oversight. We recommend this request be refused.
|
Review Type |
SA Review |
Start Date |
null |
Completed |
null |
Status |
Complete |
Review Resolution |
No Resolution Given |
Review Conclusion |
This request is being sent for a 14 day anonymous review.
|
Review Type |
Expert Group Review |
Start Date |
null |
Completed |
null |
Status |
Complete |
Review Resolution |
No Resolution Given |
Review Conclusion |
The opinion of Base Working Group was that:- Since the CONSEQUENCES OF ERRORS section of the ln description in XCU4 (pg 421) says "Default." and since the Utility Description Defaults description of CONSEQUENCES OF ERRORS on pg 15-16 says: The following apply to each utility, unless otherwise stated: A diagnostic message will be written to stderr whenever an error condition occurs. Since an exit status greater than 0 is to be used only when an error occurred, this wording requires that a diagnostic message be written. The specification does state this explicitly; there was no editorial oversight. (We intentionally decided to say this once in the front matter rather than to repeat it on every description page.) This waiver must be refused because the implementation is not meeting the explicit requirements stated in XCU4, XCU4v2, XCU5, and POSIX.2.
|
Review Type |
SA Review |
Start Date |
null |
Completed |
null |
Status |
Complete |
Review Resolution |
Rejected (REJ) |
Review Conclusion |
This request is refused.
|
Problem Reporting System Options:
|