On 07/01/2008, Paul Herring <[EMAIL PROTECTED]> wrote: > > What happens if you create a completely new directory, > > copy your current code file there, and run "mib2c-update" > > in that new directory? > > > > Do you get an error or not? > > If so, what is the output? > > It appears to have worked. Well not complained anyway. Any clues please?:
Robert's the expert on the 'mib2c-update' script. I've never used it myself (and wouldn't trust a computer to do my thinking for me!) But a quick look at the script source seems to indicate that it uses a particular hidden file to indicate when there's been a problem. The run that fails to merge the changes successfully should issue an error, telling you which file needs attention. It also leaves behind this hidden file, as a signal for the next run of the script. When you run the update script a second time (presumably having fixed whatever failed first time around), it detects this hidden file, and asks you what you want to do. If you've tweaked the code to address the original conflict, but haven't tried to merge in the changes, then choose "re-run". If you *have* merged in any changes from the mib2c template, then choose "copy". (As far as I can tell, if you choose "quit", it will simply ask you the same things all over again!) But Robert is the expert here. Dave ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ 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
