|
Home About Us A-Z Index Search * Contact Us Register Login Press ShopThe Open Brand -- Problem Reporting and Interpretations System |
Problem Report 1257 Details
Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges
This page provides all information on Problem Report 1257.
Report 1257 Actions
Problem Report Number 1257 Submitter's Classification Specification problem State Resolved Resolution Rejected (REJ) Problem Resolution ID REJ.X.0459 Raised 1970-01-01 08:00 Updated 2003-03-13 08:00 Published null Product Standard Sockets (UNIX 95) Certification Program The Open Brand certification program Test Suite VSU version 4.0.2 Test Identification Sockets/shutdown 6 Problem Summary PG4U.00006 ENOTCONN should be removed from the shutdown() spec Problem Text
Shutting down a socket without a connection is perfectly
legitimate in many situations. It may be used to specify the
socket is to be used for half-duplex operation. This can
be done before actually establishing a connection (in case of
TCP). It is also a common practice to call shutdown after
detecting an error in a socket operation which again may be
before establishing a connection.
Also since the shutdown operation is irreversible, it will not
cause any harm to call shutdown multiple times.
Therefore it does not make any sense to consider the above
cases as error cases. Subsequently it does not make sense to
set errno to ENOTCONN in these legitimate cases.
It is the author's opinion, ENOTCONN should be removed from the
specification. At most ENOTCONN should be considered only
as an optional error value.Test Output
If the implementation supports a communications domain and a
socket type: ENOTCONN in errno and return -1 on a call to int
shutdown(int socket, int how) when the socket is not connected.
JOURNAL FILE OUTPUT:
--------------------
TEST: AF_INET SOCK_STREAM
PREP: Create socket
TEST: shutdown unconnected socket for read
TEST: Return value
ERROR: shutdown call succeeded unexpectedly, returned 0
FAILReview Information
Review Type TSMA Review Start Date null Completed null Status Complete Review Recommendation No Resolution Given Review Response
While the submitter's argument may have merit, this is not a grey
area in the spec. It is clear that shutdown() should fail with
ENOTCONN if called on an unconnected socket.
This requirement is also in the POSIX sockets spec. We believe
it would be ill advised to change the X/Open spec in a manner
distancing itself from POSIX.
We recommend this request be refused.
Review Type SA Review Start Date null Completed null Status Complete Review Resolution Rejected (REJ) Review Conclusion
This request is refused. The applicant may wish to resubmit and request
a Temporary. Waiver on the grounds of a minor fault on the system being tested.
Problem Reporting System Options:
- View Report 1257
- List All PRs
- Search Reports
- Email the System Administrator
- View the The Open Brand Interpretations Database User Manual
Contact the Certification Authority