18.02.2014 Views

string

string

string

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Protocol not supported<br />

Cause<br />

The requested networking protocol has not been configured into the system, or no<br />

implementation for it exists. (A protocol is a formal description of the messages to be<br />

exchanged and the rules to be followed when systems exchange information.)<br />

Action<br />

Verify that the protocol is in the /etc/inet/protocols file and in the NIS<br />

protocols map, if applicable. If the protocol is not listed, and you want to permit its<br />

use, configure the protocol as documented or as required.<br />

Technical Notes<br />

The symbolic name for this error is EPROTONOSUPPORT, errno=120.<br />

Protocol wrong type for socket<br />

Cause<br />

This message indicates either an application programming error, or badly configured<br />

protocols.<br />

Action<br />

Make sure that the /etc/protocols file corresponds number-for-number with the<br />

NIS protocols(4) map. It it does, ask the vendor or author of the application for<br />

an update.<br />

Technical Notes<br />

A protocol was specified that does not support the semantics of the socket type<br />

requested. This amounts to a request for an unsupported type of socket. Look at the<br />

source code that made this socket request and check that it requested one of the<br />

types specified in /usr/include/sys/socket.h.<br />

The symbolic name for this error is EPROTOTYPE, errno=98.<br />

158 Solaris Common Messages and Troubleshooting Guide ♦ October, 1998

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!