2008/5/29 Jimmy Conner <[EMAIL PROTECTED]>: > Found that snmpapp.conf was 33 Megs, moving and recreating the file as now > fixed the issue. This file is filled with entries like > > engineBoots 7 > oldEngineID 0x800007e580d97c910566e83d48 > > so is it particularly needed?
Not really. The only application that seems to use this file is 'snmptrap' (when being used to send SNMPv3 traps). None of the other command-line tools will be interested in the local SNMP engine information. I've just tried this with the current development code, and it seems to update the snmpapp.conf file, replacing the old value of engineBoots, rather than appending new entries. 5.1.2 is a very old version (and no longer being supported) so this problem may well have been fixed in the last four years. Yes - it should be safe to rotate or truncate this file. All you actually need is the last 'engineBoots/oldEngineID' pair. Dave ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
