Re: ASN.1 encoder & decoder
> I looked at pyasn1. Unfortunately, it is not useful and provides a C > interface. Thanks, anyhow. pyasn1 is a pure-python implementation. C interface is not supported. > I figure that I will have to write my own, but am unsure of the best > approach. Nested lists and distionaries might be useful and I am > looking to the feasibility of those mechanisms. Try looking at the pyasn1 homepage http://pyasn1.sf.net where some design ideas were discussed. -ilya -- http://mail.python.org/mailman/listinfo/python-list
Re: PySNMP Thread unsafe?
pysnmp has been designed to be MT-safe. Although, I've never used it in a MT app, so there may be a bug showing up when you do threading... At its simplest, I'd advise snooping on the wire to make sure you are querying different devices at the same time and also to see where the [I assume] bottleneck really is -- is it in a sending or receiving phase of the query. If you could show me the code that causes the trouble? [EMAIL PROTECTED] писал(а): > I'm trying to monitor about 250 devices with SNMP, using PySNMP version > 4. I use the threading.Thread to create a threadpool of 10 threads, so > devices not responding won't slow down the monitoring process too much. > > > Here comes my problem. When using PySNMP single threaded, every this > goes well; but if I create 10 threads, it all goes awry... It seems > PySNMP is not thread safe? Can anyone elaborate on this? -- http://mail.python.org/mailman/listinfo/python-list
Re: High level SNMP
Jeremy Sanders <[EMAIL PROTECTED]> wrote: > On Thu, 09 Dec 2004 15:34:14 +0200, Petri Laakso wrote: [skipped] > The old versions of PySNMP (version 2.XX), seem to be a lot simpler to > use than later ones, so I might do that. That's if I can work out how to Recent versions tend to be more complex because they're following SNMPv3 model, which is complex. However, a simplistic high-level layer is scheduled for implementation. > convert the random string it produces to a floating point number. Somehow > it manages to gain 3 bytes over a float... Basic SNMP types don't seem to include floating point numbers. Maybe you're decoding something defined by a TEXTUAL-CONVENTION at a MIB? The protocol (for packing floating point value into some native SNMP type) might be specified by the TC then. If you provide more details I'm willing to help. -ilya -- http://mail.python.org/mailman/listinfo/python-list
