Re: [SOLVED]: the accurate description of the snmp error

On Tue, 2005-09-20 at 08:38 +0800, Ying Wang(CD) wrote:
> > With SNMPv1, a read-only community (not user) trying to
> > SET a value will result in a noSuchName error.
>
> I still think noSuchName is not a suitable error type for this case.

You are quite correct. It is not a particularly suitable error.
And in fact, the SNMPv1 specifications do define a 'readOnly'
error, intended for precisely this purpose.

Unfortunately, the Elements of Procedure were phrased in such
a way that this error is never used, and 'noSuchName' is returned
instead. Yes, this was a mistake - but it wasn't picked up in
time. So we're stuck with this unhelpful error message.

That's one of the things that was fixed in SNMPv2.

Dave


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
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/...net-snmp-users