Modified items

All recently modified items, latest first.

cnmonitor-2.1.1-1.lbn13.noarch: Get full control over your LDAP environment! Directory Server, LDAP Monitoring application. Monitoring small to large scaled deployed directory server environments. Monitoring and viewing server status can be gathered from: Open LDAP RedHat / Fedora / 389 Directory Server Sun / Oracle Directory Server Enterprise Edition Novell eDirectory Server IBM Tivoli Directory Server General Monitoring such as response time, server availability (Any LDAP Server) Features: Environment and Server availability Monitoring Verify Replication Verify Cluster / Load Balancing View Schema Verify Cache Size View Trends Get email Alerts on server failures Get email Reports of weekly load Advance LDAP Query Servers recognized: Open LDAP, RedHat / Fedora / 389 Directory Server, Sun / Oracle, Novell / Suse eDirectory, IBM Tivoli Directory Server, Netscape iPlanet, Microsoft Active Directory and Oracle Internet Directory.

charge-1.3.0-6.lbn13.x86_64: Charge is a load testing software. It allows to test what can accept an LDAP directory. An XML configuration file allows to define operations to run, the ordre of these operations and eventually to generate LDAP operations from simples rules.

c-ares-1.10.0-1.lbn13.x86_64: c-ares is a C library that performs DNS requests and name resolves asynchronously. c-ares is a fork of the library named 'ares', written by Greg Hudson at MIT.

c-ares-1.9.1-2.fc18.armv6hl: c-ares is a C library that performs DNS requests and name resolves asynchronously. c-ares is a fork of the library named 'ares', written by Greg Hudson at MIT.

bcel-5.2-7.1.fc12.x86_64: The Byte Code Engineering Library (formerly known as JavaClass) is intended to give users a convenient possibility to analyze, create, and manipulate (binary) Java class files (those ending with .class). Classes are represented by objects which contain all the symbolic information of the given class: methods, fields and byte code instructions, in particular. Such objects can be read from an existing file, be transformed by a program (e.g. a class loader at run-time) and dumped to a file again. An even more interesting application is the creation of classes from scratch at run-time. The Byte Code Engineering Library (BCEL) may be also useful if you want to learn about the Java Virtual Machine (JVM) and the format of Java .class files. BCEL is already being used successfully in several projects such as compilers, optimizers, obsfuscators and analysis tools, the most popular probably being the Xalan XSLT processor at Apache.

bastion-monit-zenoss-ldap-4.2.4_4.0.2-1.lbn13.noarch: zenperfldap start/stop/control

bastion-monit-ds389-1.4.0-1.lbn13.noarch: 389 Directory Server start/stop/control

bastion-ldapschemas-openldap-1.0.0-2.lbn13.noarch: LDAP schemas for LBN infrastructure

bastion-ldapschemas-389-1.0.0-2.lbn13.noarch: LDAP schemas for LBN infrastructure

apache-commons-validator-1.3.1-5.lbn13.noarch: A common issue when receiving data either electronically or from user input is verifying the integrity of the data. This work is repetitive and becomes even more complicated when different sets of validation rules need to be applied to the same set of data based on locale for example. Error messages may also vary by locale. This package attempts to address some of these issues and speed development and maintenance of validation rules.

apache-commons-pool-1.5.6-1.lbn13.noarch: The goal of Pool package is it to create and maintain an object (instance) pooling package to be distributed under the ASF license. The package should support a variety of pool implementations, but encourage support of an interface that makes these implementations interchangeable.

apache-commons-parent-20-1.lbn13.noarch: The Project Object Model files for the apache-commons packages.

apache-commons-logging-1.1.1-16.lbn13.noarch: The commons-logging package provides a simple, component oriented interface (org.apache.commons.logging.Log) together with wrappers for logging systems. The user can choose at runtime which system they want to use. In addition, a small number of basic implementations are provided to allow users to use the package standalone. commons-logging was heavily influenced by Avalon's Logkit and Log4J. The commons-logging abstraction is meant to minimize the differences between the two, and to allow a developer to not tie himself to a particular logging implementation.

apache-commons-lang-2.6-4.lbn13.noarch: The standard Java libraries fail to provide enough methods for manipulation of its core classes. The Commons Lang Component provides these extra methods. The Commons Lang Component provides a host of helper utilities for the java.lang API, notably String manipulation methods, basic numerical methods, object reflection, creation and serialization, and System properties. Additionally it contains an inheritable enum type, an exception structure that supports multiple types of nested-Exceptions and a series of utilities dedicated to help with building methods, such as hashCode, toString and equals.

apache-commons-jxpath-1.3-6.lbn13.noarch: Defines a simple interpreter of an expression language called XPath. JXPath applies XPath expressions to graphs of objects of all kinds: JavaBeans, Maps, Servlet contexts, DOM etc, including mixtures thereof.

apache-commons-io-2.0.1-3.lbn13.noarch: Commons-IO contains utility classes, stream implementations, file filters, and endian classes. It is a library of utilities to assist with developing IO functionality.

apache-commons-digester-1.8.1-7.lbn13.noarch: Many projects read XML configuration files to provide initialization of various Java objects within the system. There are several ways of doing this, and the Digester component was designed to provide a common implementation that can be used in many different projects

apache-commons-dbcp-1.4-7.lbn13.noarch: Many Apache projects support interaction with a relational database. Creating a new connection for each user can be time consuming (often requiring multiple seconds of clock time), in order to perform a database transaction that might take milliseconds. Opening a connection per user can be unfeasible in a publicly-hosted Internet application where the number of simultaneous users can be very large. Accordingly, developers often wish to share a "pool" of open connections between all of the application's current users. The number of users actually performing a request at any given time is usually a very small percentage of the total number of active users, and during request processing is the only time that a database connection is required. The application itself logs into the DBMS, and handles any user account issues internally.


	Copyright © 2000-2024 Corporation of Balclutha Inc. All rights reserved.