Robert Story wrote: > There is actually another proposed solution to this issue sitting in the patch > tracker. That solution would work - it does a find over all the containers > before proceeding with the insert. I'm not keen on that solution either.
For the reference, I think this is patch 1712645: [ 1712645 ] meaningful log message on duplicate IP address http://sf.net/support/tracker.php?aid=1712645 (If not, please clarify, Robert.) > I think the right way to solve this is actually by creating a new container > type - the container container. It would deal with the special case of > multiple containers, with much more flexibility and with no penalty to other > containers. It could: > > - have an option for 'all or none' inserts (optimistic) > - have an option for 'find before insert' (pessimistic) > - have options for callbacks on errors, to allow the user to decide > what to do > - allow the CONTAINER_* code to be simplified. Sounds good to me. +Thomas -- Thomas Anders (thomas.anders at blue-cable.de) ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
