ADSM-L

Re: Solaris client getting setsockopt errno=132

1998-12-08 14:29:06
Subject: Re: Solaris client getting setsockopt errno=132
From: Richard Sims <rbs AT BU DOT EDU>
Date: Tue, 8 Dec 1998 14:29:06 -0500
>     I have looked thru all the online .pdf manuals at IBM's site and can
>     not find an explaination of this error I am getting on a Solaris 2.5.1
>     machine that has ADSM v3.1.0.3 ptf3 IP21297. In the dsmerror.log file
>     I have the following  :
>
>     16:42:08 TcpOpen(): setsockopt failed on one or more options
>     19:58:34 TcpOpen(): setsockopt(SO_SNDBUF): errno = 132
>     19:58:34 TcpOpen(): setsockopt(SO_RCVBUF): errno = 132

Errors without ADSM message prefixes reflect results from calls to the
operating system.

>     can not locate errno=132

See Solaris /usr/include/sys/errno.h, which contains:
 #define ENOBUFS         132     /* No buffer space available */

You seemingly need to increase your opsys TCP/IP buffer space.

    Richard Sims, BU
<Prev in Thread] Current Thread [Next in Thread>