I'd say bug, because it also causes users created via SNMP to receive SNMPv3 informs via the target/notification MIBs to be deleted on reboot, and readOnly (according to the StorageType TC) should be saved to persistent storage, unlike nonVolatile. I submitted a patch (1642071) about this yesterday:
http://sourceforge.net/tracker/index.php?func=detail&aid=1642071&group_id=12694&atid=312694 > This doesn't quite work as you would hope though. > > While the user information is used to send the trap, the act of > configuring the "trapsess" directive causes create_user_from_session > to set the storage type for the user to "read-only". > When snmpd is stopped and it writes the persistent snmpd.conf > file, it then does not write the information back for this user, > since it ignores those entries that are not non-volatile (in > usm_save_users_from_list) - which this entry was, until messed > about with by create_user_from_session. > So, the next time you start snmpd, it stops working... > > Bug? Feature? Other? > > Phil -- Michael Kirkham President & CEO Muonics, Inc. http://www.muonics.com/ ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
