OK - I've got a patch implementing the OID.*-style syntax waiting to be applied when I get to work in the morning.
There's just one issue outstanding: TS> Is there a subtle (or not so, for any shell addicts) difference between TS> "oid.*" (doesn't match oid itself?) and "oid*" (matches oid itself?) Do we want to distinguish between these two cases? I can code it either way. Is this sort of flexibility worth supporting? Doing so makes things slightly harder to document (and/or understand), but my gut reaction is that it's probably a useful distinction to be able to make. In practise, it's likely (?inevitable) that if ".some.enterprise.oid.0.N" is a valid trap OID, then ".some.enterprise.oid" (or ".some.enterprise.oid.0") will not be. So it's perhaps sensible to allow an admin to configure things as such. I'm therefore strongly tempted to tweak the current patch to make this distinction. But I'm willing to be persuaded otherwise, if this is felt to be unnecessary. Thoughts? Dave ------------------------------------------------------------------------- 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-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
