From owner-freebsd-current@FreeBSD.ORG  Fri Jan 16 08:39:59 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D0ACF16A4CE
	for <current@freebsd.org>; Fri, 16 Jan 2004 08:39:59 -0800 (PST)
Received: from pandora.afflictions.org (asylum.afflictions.org [64.7.134.90])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3AD5143D5A
	for <current@freebsd.org>; Fri, 16 Jan 2004 08:39:58 -0800 (PST)
	(envelope-from dgerow@afflictions.org)
Received: from dementia.afflictions.org (dementia [172.16.0.56])
	by pandora.afflictions.org (Postfix) with ESMTP id E0D0A5C0AE
	for <current@freebsd.org>; Fri, 16 Jan 2004 12:09:23 -0500 (EST)
Received: by dementia.afflictions.org (Postfix, from userid 1001)
	id F004A6D457; Fri, 16 Jan 2004 11:41:35 -0500 (EST)
Date: Fri, 16 Jan 2004 11:41:35 -0500
From: Damian Gerow <dgerow@afflictions.org>
To: current@freebsd.org
Message-ID: <20040116164135.GA42868@afflictions.org>
References: <20040115213447.GA40114@afflictions.org>
	<Pine.NEB.3.96L.1040115183701.77946B-100000@fledge.watson.org>
	<mailman.1074228420.50145.fcurrent-l@lists.sentex.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <mailman.1074228420.50145.fcurrent-l@lists.sentex.ca>
X-Operating-System: FreeBSD 5.2-RC on a i386
X-GPG-Fingerprint: B3D7 D901 A53A 1A99 BFD6  E6DF 9F3B 742B C288 9CC9
User-Agent: Mutt/1.5.5.1i
Subject: Re: Problems with net/net-snmp on 5.2-RELEASE?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Jan 2004 16:39:59 -0000

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.