Dave Shield wrote:
> On 26/10/06, Thomas Anders <[EMAIL PROTECTED]> wrote:
>>I'd propose to change the check_set_error function name
>> to something that's prefixed by "netsnmp_" (clean namespace).
>
> I'd also suggest some indication that this is specific to the "pass"
> mechanism.
> "ch
On 26/10/06, Thomas Anders <[EMAIL PROTECTED]> wrote:
>I'd propose to change the check_set_error function name
> to something that's prefixed by "netsnmp_" (clean namespace).
I'd also suggest some indication that this is specific to the "pass" mechanism.
"check_set_error" feels too much li
Done . Request #1585146.
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0
Anthony Novatsis wrote:
> I've created two patches (one for pass.c and the other for pass_persist.c)
> for the Net-SNMP version 5.4.pre4 files (but to be considered for a future
> 5.4.x release).
Can you upload them to our patches tracker (www.net-snmp.org/patches),
please?
Before you do, I'd pro
I've created two patches (one for pass.c and the other for pass_persist.c) for the Net-SNMP version 5.4.pre4 files (but to be considered for a future 5.4.x release).Basically I created the function check_set_error() which checks for possible error strings in response to a pass-through set request a
> "AN" == Anthony Novatsis <[EMAIL PROTECTED]> writes:
AN> Firstly, is there any reason to make a difference between the errors that
AN> can be returned with pass and pass_persist in version 5.4?
Many times we include features that we receive patches for and though
ideally it would be nice if
On 25/10/06, Thomas Anders <[EMAIL PROTECTED]> wrote:
> Anthony Novatsis wrote:
> > Firstly, is there any reason to make a difference between the errors that
> > can be returned with pass and pass_persist in version 5.4?
> >
> > Secondly, is there any special reason why the full range of SNMPv2 err
Anthony Novatsis wrote:
> Firstly, is there any reason to make a difference between the errors that
> can be returned with pass and pass_persist in version 5.4?
>
> Secondly, is there any special reason why the full range of SNMPv2 error
> codes cannot be returned? From what I can see, it is fair
Dear All,In a Net-SNMP version 5.3.1 pass-through executable (either pass or pass_persist), it is only possible to return the errors wrongType(7) or notWritable(17) in response to a set request by writing the string "wrong-type" or "not-writable" respectively.
In version 5.4, I have seen in the sou