Date: Thu, 26 Jan 2006 14:29:19 +0300 From: Andrew Pantyukhin <infofarmer@gmail.com> To: FreeBSD Questions <questions@freebsd.org> Subject: Buffer space and socket syscall tracing Message-ID: <cb5206420601260329k2fd1f678l2714647b62a07391@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
I've stumbled upon the infamous "No buffer space available" problem (with thousands of netgraph nodes). I'm wondering if there's a really comprehensive way to debug it. I know that it's probably a matter of some sysctl, but I've googled and tuned for days - and I now feel that there must be another way. Truss and ktrace both say that the error is generated when a socket syscall is made. Is there a way to trace inside the syscall and find the very particular reason for this? I know that it might not be of any use to me as I'm not any kind of kernel hacker, but I want to give it a shot. Thanks
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cb5206420601260329k2fd1f678l2714647b62a07391>