|
Home About Us A-Z Index Search * Contact Us Register Login Press ShopThe Open Brand -- Problem Reporting and Interpretations System |
Problem Report 1649 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 1649.
Report 1649 Actions
Problem Report Number 1649 Submitter's Classification Test Suite problem State Resolved Resolution Permanent Interpretation (PIN) Problem Resolution ID PIN.X.0206 Raised 2002-10-03 08:00 Updated 2003-03-13 08:00 Published 2002-10-14 08:00 Product Standard Sockets V2 (UNIX 98) Certification Program The Open Brand certification program Test Suite VSU version 5.1.2 Test Identification CAPI.os/sockets/listen 3 Specification Networking Services Issue 5 Location in Spec See Problem Text Problem Summary PIN4U.00072 This IR claims that historical listen() behavior should be allowed in UNIX98 Problem Text
Note that we calculate the true qlimit with the following formula:
The system actually enforces the limit of pending connections as
((3 * backlog) / 2) + 1
We did the right thing by converting a negative backlog value to 0. Then
the qlimit will be 1 based on the formula. That was why the connect call
succeeded.
One problem here: with this formula and we convert all negative value to 0,
we can not create a situation of qlimit of 0. We believe that the
test should not require that the connect call not succeed in this
case.Test Output
PREP: Get VSU_CONNECT_TIMEOUT configuration variable
TEST: AF_INET SOCK_STREAM
PREP: Create test sockaddr_in: address = 130.62.32.200, port = 3525
PREP: Child: create socket
PREP: Child: bind to socket
PREP: Child: listen on socket with backlog of -1
PREP: Child: tell parent ready
PREP: Child: wait for parent to complete test
PREP: Create a socket
PREP: Wait for child to be ready
TEST: connect is rejected
TEST: Return value
ERROR: connect call succeeded unexpectedly, returned 0Review Information
Review Type TSMA Review Start Date null Completed null Status Complete Review Recommendation No Resolution Given Review Response
This request concerns the same issue as PIN4U.00046.
Although the wording of the specification changed slightly between
XNS4 and XNS5, the same grey area still exists in XNS5, and so a new
PIN should be issued that can be referenced in UNIX98 registrations.
It is recommended that a permanent interpretation is granted.
Review Type SA Review Start Date null Completed null Status Complete Review Resolution Permanent Interpretation (PIN) Review Conclusion
A Permanent Interpretation is granted.
Problem Reporting System Options:
- View Report 1649
- List All PRs
- Search Reports
- Email the System Administrator
- View the The Open Brand Interpretations Database User Manual
Contact the Certification Authority