> What changed between 5.0.x and 5.1.x with respect to the custom "exec"
> MIB?
The internal implemenmtation of this facility changed quite significantly
between the 5.0.x and 5.1.x lines. In particular, it now uses the v5
handler-based API (rather than the old v4 API), and caches the output
internally, rather than relying on a single external file (4.2.x) or
not caching it at all (5.0.x)
When working properly, this means that the cached output of one exec
directive won't interfere with that of another (as happened previously),
and even allows the caching to be managed via SNMP.
Of course that doesn't help if the thing doesn't actually work for you!
The first thing that I'd be inclined to check is whether this problem
is triggered by the output that's being read in (perhaps the size of it),
or whether it's connected to the command being run (e.g. length of time
to finish).
Could you please try something like the following:
$ /usr/platform/sun4u/sbin/prtdiag -v > /tmp/prtdiag
$ /usr/sbin/prtconf -pv > /tmp/prtconf
$ /usr/bin/ps -ae -o user,pid,ppid,args > /tmp/ps
and then tweak the exec lines to look at these three files instead:
exec .1.3.6.1.4.1.2021.50 prtdiag cat /tmp/prtdiag
exec .1.3.6.1.4.1.2021.51 prtconf cat /tmp/prtconf
exec .1.3.6.1.4.1.2021.52 ps cat /tmp/ps
The data will be out of date, of course, but should help pinpoint where
the problem lies....
> Is this related to the errors I'm getting at configure time (other
> thread) for 5.1.x that I'm not getting for 5.0.9?
Possible I suppose, but somewhat unlikely.
I think this is much more likely to be related to the "exec" changes
that went in between 5.0.x and 5.1
One final note - an advance warning if you like.
The 5.2 release will include a new MIB that provides an alternative
to the old UCD-SNMP-MIB::extTable, and we'll slowly be moving towards
using that NET-SNMP-EXTEND-MIB instead.
This won't affect the UCD-SNMP-MIB::extTable itself, but it *will*
affect the sort of "relocatable exec" directive that you've got above.
In particular, the MIB format that this outputs will (eventually) change.
Now don't worry - we're not talking about doing this overnight.
The current style will certainly be supported in 5.2 and 5.3.
But it'll be marked as "deprecated" with 5.3, and will probably
start issuing a warning. And the format is not going to change
until a 5.4 release at the very earliest.
But it might be worth looking at the NET-SNMP-EXTEND-MIB approach
as soon as 5.2 becomes available.
(Oh, and the reason for the change is that the current multi-line
output is not actually a legal MIB structure!)
Dave
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.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
