>Is net-snmp stable and reliable enough to use in a high-reliability
embedded system?

Your mileage may vary.  Certainly there's plenty of people using it
day-to-day who are knowledgeable enough to spot obvious problems and willing
to comment about them.  Hence...

>I've seen many mails mentioning crashes and memory leaks.  Looks like these
are usually development problems.  Can we expect a typical net-snmp system
to run for years under normal conditions?

Certainly there's lots of crashes with new code.  As you've noticed, these
tend to work out.  I personally haven't had the experience of running it for
years because I tend to upgrade for new features (or write them myself).
Nevertheless, I don't see why it shouldn't.  Your mileage may vary.

>Is net-snmp generally considered competitive with commercial vendors for
developing commercial systems?

My experience is with Sun products.  They have adopted net-snmp and
contributed code.

>I know LINUX is now being positioned that way, with resellers doing
packaging, testing, and support for real time systems.  Is anyone doing this
or planning this for net-snmp?

(pass)

>One more high-level thing:  Why are you doing this?  What motivates all
this work on SNMP?  How do you make a living on it?  (Forgive me if I'm
being crass, mentioning profitability here.  I'm still new to open source!)

I need it.  It's as simple as that.  My job is to maintain UNIX servers.  I
can't be running around building to building staring at monitors.  I can't
be constantly logging in checking and checking things.  I need a way to
monitor them quickly, efficiently and quietly.  My vendor's product was IMHO
bloated, broken and lacking features.  My boss wanted the system to "make my
cell phone ring if a fan blows".  The vendor's product wouldn't do that, so
I wrote the damn thing myself.  Net-snmp gave me the framework, I just had
to contribute my proprietary code.  I get paid to keep the servers running.
My employers were originally hostile to open source until they didn't have
any choice - no vendor was supplying what they wanted (in that case, SAMBA).
Now (judging from the noise in the press), it's the wave of the future.
Everybody's using it because everybody's using it.  The development process
is open to scrutiny; download the source and read it, compile the thing for
yourself, subscribe to the mailing lists and watch the fur fly.  If it's
busted, fix it.




This communication is intended for the use of the recipient to which it is
addressed, and may contain confidential, personal and or privileged
information. Please contact us immediately if you are not the intended
recipient of this communication, and do not copy, distribute, or take action
relying on it. Any communication received in error, or subsequent reply,
should be deleted or destroyed.



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
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

Reply via email to