Environment Specification

A product may be registered in all members of a binary-compatible family
of products on the basis of a single test report.

Answer the questions for each binary-compatible family. Alternately, provide
the answers in the Appendix at the end of this
document.

Testing Environment

Binary-compatible Family

Portability Environment

Indicator of Compliance

Compliance Details

Test Suite:
Test Report:

Test Suite:
Test Report:

Test Suite:
Test Report:

Test Suite:
Test Report:

Test Suite:
Test Report:

Temporary Waivers

Enter the waiver number and expiry date for each temporary waiver granted by The Open Group.

Waiver Number

Expiry Date

1.1 Limits

1.1.1 Listen Queues

Question 1: What is the limit the implementation places on the
length of a socket's listen queue?

Response

Indicate the implementation's limit on the length of the socket's
listen queue, or "None" if no limit is imposed.

Rationale

The specification states that an implementation may limit the length
of a socket's listen queue, and that this limit may be imposed if the
setting of the backlog argument exceeds an
implementation-dependent maximum value.

1.2 Reference Manual Pages

1.2.1 Error Numbers

Question 2: Which of the following optional errors,
( denoted by "may fail" in the specification ), listed in
the Reference Manual Pages are detected in the circumstances specified?

Response

Function

Error

Detected

accept()

ENOMEM

Yes
No

ENOBUFS

Yes
No

ENOSR

Yes
No

EPROTO

Yes
No

bind()

EACCESS

Yes
No

EINVAL

Yes
No

EISCONN

Yes
No

ENAMETOOLONG

Yes
No

ENOBUFS

Yes
No

ENOSR

Yes
No

connect()

EACCESS

Yes
No

EADDRINUSE

Yes
No

ECONNRESET

Yes
No

EHOSTUNREACH

Yes
No

EINVAL

Yes
No

ENAMETOOLONG

Yes
No

ENETDOWN

Yes
No

ENOBUFS

Yes
No

ENOSR

Yes
No

EOPNOTSUPP

Yes
No

fgetpos()

ESPIPE

Yes
No

fsetpos()

ESPIPE

Yes
No

ftell()

ESPIPE

Yes
No

getpeername()

ENOBUFS

Yes
No

ENOSR

Yes
No

getsockname()

EINVAL

Yes
No

ENOBUFS

Yes
No

ENOSR

Yes
No

getsockopt()

EACCESS

Yes
No

EINVAL

Yes
No

ENOBUFS

Yes
No

ENOSR

Yes
No

listen()

EACCESS

Yes
No

EINVAL

Yes
No

ENOBUFS

Yes
No

recv()

EIO

Yes
No

ENOBUFS

Yes
No

ENOMEM

Yes
No

ENOSR

Yes
No

recvfrom()

EIO

Yes
No

ENOBUFS

Yes
No

ENOMEM

Yes
No

ENOSR

Yes
No

recvmsg()

EIO

Yes
No

ENOBUFS

Yes
No

ENOMEM

Yes
No

ENOSR

Yes
No

send()

EACCESS

Yes
No

ENETDOWN

Yes
No

ENETUNREACH

Yes
No

ENOBUFS

Yes
No

ENOSR

Yes
No

EIO

Yes
No

sendmsg()

EACCESS

Yes
No

EDESTADDRREQ

Yes
No

EHOSTUNREACH

Yes
No

EIO

Yes
No

EISCONN

Yes
No

ENAMETOOLONG

Yes
No

ENETDOWN

Yes
No

ENETUNREACH

Yes
No

ENOBUFS

Yes
No

ENOMEM

Yes
No

ENOSR

Yes
No

sendto()

EACCESS

Yes
No

EDESTADDRREQ

Yes
No

EHOSTUNREACH

Yes
No

EINVAL

Yes
No

EIO

Yes
No

EISCONN

Yes
No

ENAMETOOLONG

Yes
No

ENETDOWN

Yes
No

ENETUNREACH

Yes
No

ENOBUFS

Yes
No

ENOMEM

Yes
No

ENOSR

Yes
No

setsockopt()

ENOMEM

Yes
No

ENOBUFS

Yes
No

ENOSR

Yes
No

shutdown()

ENOBUFS

Yes
No

ENOSR

Yes
No

socket()

EACCESS

Yes
No

ENOBUFS

Yes
No

ENOMEM

Yes
No

ENOSR

Yes
No

socketpair()

EACCES

Yes
No

ENOMEM

Yes
No

ENOBUFS

Yes
No

ENOSR

Yes
No

Rationale

Each of the above error conditions is marked as optional in the
Reference Manual Pages and an implementation may return this error
in the circumstances specified or may not provide the error indication.