Folks,
there are two issues with the EVAL classified snmpdx package
you should be aware of.

    **** INFINITE LOOP ****

A compatiblity problem between snmpdx and perl. Problematic version
combinations cause a infinite loop in snmpdx that consumes large amounts
of CPU horsepower and fills the logging filesystem at a very fast rate
as far as it will go.

     snmpdx      perl
    <= 0.2.8  <= 5.8.3  ok
    <= 0.2.8  >= 5.8.4  problem
    >= 0.2.9     5.8.x  ok

Please either
- keep your old perl-5.8.3 or earlier version or
- upgrade to snmdx-0.2.9 or later or
- apply OSSP patch [1] for locally modified packages

    **** BIND PROBE ****

Also note that today snmpdx-0.2.10 was released which adds a swBind
probe for monitoring named(8). In order to get this new probe to work
the "statistics-file" in named.conf(5) must be configured as shown
in the CURRENT named package [2]. This is not the default case for
any existing RELEASE. There are no plans for issuing an UPD bind
package because a modified named.conf file will inadvertently create
a named.conf.rpmsave and cause problems for people running automated
update environments.

[1] http://cvs.ossp.org/chngview?cn=4652
[2] http://cvs.openpkg.org/chngview?cn=18358

--
[EMAIL PROTECTED], Cable & Wireless
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
User Communication List                      [EMAIL PROTECTED]

Reply via email to