| |
Home About Us A-Z Index Search • |
Organization | Santa Cruz Operation |
---|---|
Author | John Farley |
Product Identification | Version/Release Number | Product Supplier | |
---|---|---|---|
1. | UnixWare | 2.1.1 |
Testing Environment | Binary-compatible Family | Portability Environment | Indicator of Compliance | Compliance Details | |
---|---|---|---|---|---|
1. |
|
| Test Report from Test Suite | Test Suite:
VSU4.1.0C Test Report: UW211_UNIX95 |
Question 1: Which socket domains are supported by the implementation?
Response
Domain | Type | Protocol | |
---|---|---|---|
1. | AF_INET | SOCK_STREAM | TCP |
2. | AF_INET | SOCK_DGRAM | UDP |
3. | AF_UNIX | AOCK_STREAM | none |
Rationale
The CAE Specification, Networking Services, Issue 4, defines that the domains, socket types and protocols supported by a conforming system are implementation-dependent. Component Definitions, Issue 2, states that products conforming to the Sockets Product Standard definition shall be available in configurations that support the following socket domains:
Reference
CAE Specification, Networking Services, Issue 4, Chapter 8, Sockets Interfaces, socket().
Sockets Product Standard Definition.
Question 2: What is the limit the implementation places on the length of a socket's listen queue?
Response
The implementation does not impose a limit on the length ofthe queue apart from that imposed by the type of the lengthfield which on this implementation is an int.
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.
Reference
CAE Specification, Networking Services, Issue 4, Chapter 8, Sockets Interfaces, listen().
Question 3: Which of the following optional errors listed in the Reference Manual Pages are detected in the circumstances specified?
Response
Function | Error | Detected |
---|---|---|
accept() | ENOMEM | Yes |
ENOBUFS | Yes | |
ENOSR | Yes | |
EPROTO | Yes | |
bind() | EINVAL | Yes |
EISCONN | Yes | |
ENAMETOOLONG | Yes | |
ENOBUFS | Yes | |
ENOSR | Yes | |
connect() | EADDRINUSE | Yes |
ECONNRESET | Yes | |
EHOSTUNREACH | Yes | |
EINVAL | Yes | |
ENAMETOOLONG | Yes | |
ENETDOWN | Yes | |
ENOBUFS | Yes | |
ENOSR | Yes | |
EOPNOTSUPP | No | |
fgetpos() | ESPIPE | Yes |
fsetpos() | ESPIPE | Yes |
ftell() | ESPIPE | Yes |
getpeername() | ENOBUFS | Yes |
ENOSR | Yes | |
getsockname() | EINVAL | Yes |
ENOBUFS | Yes | |
ENOSR | Yes | |
getsockopt() | EINVAL | Yes |
ENOBUFS | Yes | |
ENOSR | Yes | |
listen() | EINVAL | Yes |
ENOBUFS | Yes | |
recv() | EIO | Yes |
ENOBUFS | Yes | |
ENOMEM | Yes | |
ENOSR | Yes | |
recvfrom() | EIO | Yes |
ENOBUFS | Yes | |
ENOMEM | Yes | |
ENOSR | Yes | |
recvmsg() | EINVAL | No |
EIO | Yes | |
ENOBUFS | Yes | |
ENOMEM | Yes | |
ENOSR | Yes | |
send() | ENETDOWN | No |
EHOSTUNREACH | Yes | |
ENOBUFS | Yes | |
ENOSR | Yes | |
EIO | Yes | |
sendmsg() | EDESTADDRREQ | Yes |
EHOSTUNREACH | Yes | |
EINVAL | Yes | |
EIO | Yes | |
EISCONN | No | |
ENAMETOOLONG | Yes | |
ENETDOWN | No | |
ENETUNREACH | Yes | |
ENOBUFS | Yes | |
ENOMEM | Yes | |
ENOSR | Yes | |
sendto() | EDESTADDRREQ | Yes |
EHOSTUNREACH | Yes | |
EINVAL | Yes | |
EIO | Yes | |
EISCONN | No | |
ENAMETOOLONG | Yes | |
ENETDOWN | No | |
ENETUNREACH | Yes | |
ENOBUFS | Yes | |
ENOMEM | Yes | |
ENOSR | Yes | |
setsockopt() | ENOMEM | Yes |
ENOBUFS | Yes | |
ENOSR | Yes | |
shutdown() | ENOBUFS | Yes |
ENOSR | Yes | |
socket() | ENOBUFS | Yes |
EMNOMEM | Yes | |
ENOSR | Yes | |
socketpair() | EACCES | Yes |
ENOMEM | Yes | |
ENOBUFS | Yes | |
ENOSR | Yes |
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.
Reference
CAE Specification, Networking Services, Issue 4, Chapter 8, Sockets Interfaces, ERRORS.
Copyright © 1997 Santa Cruz Operation
All rights reserved.
Date | Name | Comment |
---|---|---|
27-Aug-1997 | ApTest | Initial data entry |
The Open Group and Boundaryless Information Flow are trademarks and UNIX is a registered trademark of The Open Group in the United States and other countries. All other trademarks are the property of their respective owners.