From owner-freebsd-hackers Wed Nov 20 12:04:50 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA01011 for hackers-outgoing; Wed, 20 Nov 1996 12:04:50 -0800 (PST) Received: from haywire.DIALix.COM (haywire.DIALix.COM [192.203.228.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA01004 for ; Wed, 20 Nov 1996 12:04:46 -0800 (PST) Received: (from news@localhost) by haywire.DIALix.COM (8.8.2/8.8.2) id EAA20201 for freebsd-hackers@freebsd.org; Thu, 21 Nov 1996 04:04:36 +0800 (WST) X-Authentication-Warning: haywire.DIALix.COM: news set sender to usenet-request@haywire.dialix.com using -f Received: from GATEWAY by haywire.DIALix.COM with netnews for freebsd-hackers@freebsd.org (problems to: usenet@haywire.dialix.com) To: freebsd-hackers@freebsd.org Date: 20 Nov 1996 20:04:35 GMT From: peter@spinner.DIALix.COM (Peter Wemm) Message-ID: <56vo8j$irv$1@haywire.DIALix.COM> Organization: DIALix Services, Perth, Australia. References: <199611182122.OAA09009@hemi.com> Subject: Re: Help: ucd-snmpd w/freebsd Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article , jc@irbs.com (John Capo) writes: > Quoting Ade Barkah (mbarkah@hemi.com): >> Hello, >> >> I'm getting rather frustrated trying to get an snmpd running for >> FreeBSD 2.1 machines. Please help! =-) Problem: the interface counters >> never seem to get updated once snmpd is running. >> >> Example. (on a pretty busy system network-wise): >> >> $ snmpget -v 1 localhost public interfaces.ifTable.ifEntry.ifInOctets.1 >> interfaces.ifTable.ifEntry.ifInOctets.1 = 558046531 >> >> (five minutes later) >> >> $ snmpget -v 1 localhost public interfaces.ifTable.ifEntry.ifInOctets.1 >> interfaces.ifTable.ifEntry.ifInOctets.1 = 558046531 >> > > The result of the last request is cached by snmpd. I haven't looked > at the code to see if this is a feature or not. Query another > variable then query ifInOctets.1 again and you should see that it > has changed. > > John Capo I ran into this when setting up mrtg, and disabled the "optimisation" in the snmpd code. I was unsure whether to commit the patch to the ports collection, it makes very little difference in cpu resource consumption but certainly makes a lot of strange side effects disappear. -Peter