Problems with net/net-snmp on 5.2-RELEASE?
dgerow at afflictions.org
Fri Jan 16 08:39:59 PST 2004
Thus spake Damian Gerow (dgerow at afflictions.org) [15/01/04 23:47]:
: The abort happens when polling for .188.8.131.52.4.1.2021.10.1.5.1 and
: .184.108.40.206.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
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.
More information about the freebsd-current