Re: setsockopt 228K fails with ERR#55 'No buffer space available'

Thanks dan but I already tried that and it doesn't work but maxsockbuf does. Really looking for the affects that altering that might have and if its a good idea. 256k send and receive buffers on a socket seem very large to me. Steve - Original Message - From: "Dan Nelson" <[EMAIL PRO

Re: setsockopt 228K fails with ERR#55 'No buffer space available'

In the last episode (Sep 11), Steven Hartland said: > The following fails with ERR#55 'No buffer space available' > int buf_size = (228*1024); > int ret = setsockopt( s, SOL_SOCKET, SO_SNDBUF, (void*) &buf_size, sizeof( > buf_size ) ); > > This appears like its controlled by kern.ipc.maxsockbuf w

setsockopt 228K fails with ERR#55 'No buffer space available'

The following fails with ERR#55 'No buffer space available' int buf_size = (228*1024); int ret = setsockopt( s, SOL_SOCKET, SO_SNDBUF, (void*) &buf_size, sizeof( buf_size ) ); This appears like its controlled by kern.ipc.maxsockbuf which is default of 256k so the above should work if its per soc