Date: Fri, 16 Jan 2004 11:41:35 -0500 From: Damian Gerow <dgerow@afflictions.org> To: current@freebsd.org Subject: Re: Problems with net/net-snmp on 5.2-RELEASE? Message-ID: <20040116164135.GA42868@afflictions.org> In-Reply-To: <mailman.1074228420.50145.fcurrent-l@lists.sentex.ca> References: <20040115213447.GA40114@afflictions.org> <Pine.NEB.3.96L.1040115183701.77946B-100000@fledge.watson.org> <mailman.1074228420.50145.fcurrent-l@lists.sentex.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Thus spake Damian Gerow (dgerow@afflictions.org) [15/01/04 23:47]: : The abort happens when polling for .1.3.6.1.4.1.2021.10.1.5.1 and : .1.3.6.1.4.1.2021.10.1.5.2 -- ucdavis.laTable.laEntry.laLoadInt.1 and .2, : respectively. I'm not sure why, exactly, as I haven't had the time to go : into in-depth debugging. A quick attempt at running it through truss gives : me this: : : newhost# truss -o snmpd.out snmpd -DALL -Lf snmpd.debug -f : truss: truss: cannot open /proc/curproc/mem: No such file or directory : cannot open /proc/13877/mem: No such file or directory : newhost# Since I didn't make this clear, yes, I'm aware this is a problem with truss, and not with snmpd... I have some more time to look through it today, I'll see what I can find.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040116164135.GA42868>