Location | Meaning | Action |
|
|
|
5 | OUTPRO received a signal | This error requires HP |
| indicating that a root socket had | notification. |
| a control message on it, and yet |
|
| the socket was not in a state |
|
| that permitted these messages. |
|
| The xx field of the log record |
|
| header contains the global |
|
| socket descriptor of the socket |
|
| that encountered the problem |
|
| and the yy field contains the |
|
| state (so_b.state) the socket |
|
| was in. This is an NS ARPA |
|
| internal error. |
|
|
|
|
6 | OUTPRO received a signal | This error requires HP |
| indicating that a root socket had | notification. |
| some undefined message on it. |
|
| The xx field of the log record |
|
| header contains the global |
|
| socket descriptor of the socket |
|
| that encountered the error. This |
|
| is an NS ARPA internal error. |
|
|
|
|
7 | OUTPRO received a signal | This error requires HP |
| indicating that a socket had | notification. |
| some message on it, but the |
|
| socket is of an undefined kind. |
|
| The xx field of the log record |
|
| header contains the global |
|
| socket descriptor of the socket |
|
| that encountered the error and |
|
| the yy field contains the |
|
| socket_kind field of the |
|
| socket. This is an NS ARPA |
|
| internal error. |
|
|
|
|
8 | OUTPRO received a signal | This error requires HP |
| indicating that a VC socket had | notification. |
| an exception on it, but the |
|
| socket was not in a state that |
|
| permitted that kind of signal. |
|
| The xx field of the log record |
|
| header contains the global |
|
| socket descriptor of the socket |
|
| that encountered the error and |
|
| the yy field contains the |
|
| socket_b.state field of the |
|
| socket. This is an NS ARPA |
|
| internal error. |
|
|
|
|
650 Logging Codes and Messages