On Mon, Apr 11, 2011 at 11:56:26AM +0400, Gleb Smirnoff wrote: T> On Mon, Apr 11, 2011 at 02:21:30PM +0700, Eugene Grosbein wrote: T> E> On 11.04.2011 13:54, Przemyslaw Frasunek wrote: T> E> >> IMO, any kind of memory allocation code (malloc, uma, netgraph item T> E> >> allocator) never return EPERM, they return ENOMEM or ENOBUFS. T> E> >> T> E> >> So, there is a bug somewhere else. T> E> > T> E> > I think so, but for me it still looks like resource shortage. As I wrote T> E> > before, when EPERM starts appearing, I'm unable to run "ngctl list". T> E> T> E> Increase sysctl kern.ipc.maxsockbuf. T> E> I was forced to rise it upto 80MB (sic!) as 8MB was not enough to me. T> T> Ah, I found where EPERM comes from. Will fix it soon.
Sorry, I was wrong :( -- Totus tuus, Glebius. _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
