Code

Meaning

Action

 

 

 

34

Aborted locally. The protocol

The socket through which the

 

referenced by the socket

error has been reported cannot

 

specified has indicated that the

be recovered and should be

 

socket can no longer be

released via IPCShutDown. A

 

supported. This error will be

later attempt to reestablish a

 

returned only after the protocol

failed connection may work if

 

has determined that the remote

the underlying problem is

 

node can no longer be reached

corrected (e.g., if a crashed

 

(either because it has crashed

node is rebooted, if the links of a

 

or the network connecting the

partitioned network are repaired,

 

local node to it has become

or if a heavily congested

 

partitioned). Under certain

network has become less

 

conditions, this error may be

congested).

 

reported if the network becomes

 

 

heavily congested.

 

 

 

 

35

Name limit. The caller

The calling process must assign

 

attempted to assign too many

fewer names to the referenced

 

names to the referenced socket

socket.

 

with IPCName.

 

 

 

 

36

Name table full. A process

Release some of the names that

 

attempted to bind a name to a

are bound to sockets. This may

 

socket via IPCGive or IPCName

be done using either

 

when the system had no free

IPCNamErase or IPCGet.

 

name records. A name record

Because name records are

 

must be allocated for each

systemwide resources shared

 

name that is bound to a socket.

by all NSARPA programs, the

 

When the system runs out of

name records released by one

 

name records, all succeeding

program may be allocated for

 

IPCGive and IPCName

use by another.

 

requests are rejected.

 

 

 

 

37

Name not found. A process

One or both of the following

 

attempted to obtain a path

actions may be taken: (1) Make

 

report descriptor using

sure that the name specified in

 

IPCLookUp, but the name

the IPCLookUp call was the one

 

specified in the call was not

that was intended; (2) consider

 

registered in the referenced

that the failure could have been

 

socket registry.

due to a race condition (the

 

 

IPCLookUp caller could have

 

 

executed its call before the

 

 

IPCName caller executed its

 

 

call).

 

 

 

38

No ownership. The caller

Check that the name specified is

 

invoked IPCNamErase

the one the caller intended to

 

specifying a valid name but one

use.

 

bound to a socket that it does

 

 

not own. Only the owner of a

 

 

call socket may purge its name.

 

 

 

 

39

Illegal registry name. The caller

Verify that the name passed was

 

invoked IPCLookUp, passing it

the intended one or verify that

 

a node name having an illegal

the length specified for the

 

syntax (for example, too many

passed name was correct.

 

levels of hierarchy or too many

 

 

characters in one of the name

 

 

parts).

 

 

 

 

Numeric Error Codes 213