Search results

python-yapps2-2.2.0-1.lbn25.noarch

YAPPS is an easy to use parser generator that is written in Python and generates Python code. There are several parser generator systems already available for Python, but this parser has different goals: Yapps is simple, very easy to use, and produces human-readable parsers. It is not the fastest or most powerful parser. Yapps is designed to be used when regular expressions are not enough and other parser systems are too much: situations where you might otherwise write your own recursive descent parser. This package contains several upward-compatible enhancements to the original YAPPS source: - Handle stacked input ("include files") - augmented ignore-able patterns (can parse multi-line C comments correctly) - better error reporting - read input incrementally

python-yaql-0.3-1.lbn19.noarch

Yet Another Query Language

python-zaqarclient-0.2.0-1.lbn19.noarch

Python client to Zaqar messaging service API v1

python-ZConfig-3.0.4-2.lbn19.noarch

ZConfig is a configuration library intended for general use. It supports a hierarchical schema-driven configuration model that allows a schema to specify data conversion routines written in Python. ZConfig's model is very different from the model supported by the ConfigParser module found in Python's standard library, and is more suitable to configuration-intensive applications.

python-zdaemon-4.3-1.lbn25.noarch

Daemon process control library and tools for Unix-bases systems.

python-zdaemon-4.3-1.lbn25.noarch

Daemon process control library and tools for Unix-bases systems.

python-zenemailevent-1.0.1-1.lbn13.noarch

If you use an MTA which can forward mail via a pipe, then you can set up mailbox(s) to collect emails and send them to your Zentinel/ZEP with this program. Here is an example using the Courier MTA and Courier Maildrop (see dot-courier and maildrop manpages in the courier-mta for further explanation), but it should work with many other forwarders. There are further options - try /usr/bin/zenemailevent --help for more details. In the $HOME of your mail user (zenoss@domain.com say), place the following (customised for your setup) in the .courier and .courier-default files: | /usr/bin/zenemailevent -u admin -p password -s http://zenoss.domain.com:8080 If you direct mail to zenoss@domain.com, it will be forwarded to your Zentinel with a default severity of info. If you send to zenoss-critical@domain.com, it'll have a Critical severity. The default event class is /Status/Update. The component and the device are calculated from the Sender/From header as component@device. As it is trivially easy to 'spoof' these, you have considerable flexibility in assuring email events are bound to their associated device(s). A real-world configuration of Monit's email alerting is as simple as (in /etc/monitrc): set mail-format { from: monit@mydevice.domain.com subject: $SERVICE $EVENT message: $ACTION: $DESCRIPTION } set alert zenoss@domain.com # Send alert to system admin on any event This will register Monit emails as info events on the /Device mydevice.domain.com. Note that because we've also removed $DATE markers from the message, monit events will roll-up.

python-zenemailevent-1.0.1-1.lbn13.noarch

If you use an MTA which can forward mail via a pipe, then you can set up mailbox(s) to collect emails and send them to your Zentinel/ZEP with this program. Here is an example using the Courier MTA and Courier Maildrop (see dot-courier and maildrop manpages in the courier-mta for further explanation), but it should work with many other forwarders. There are further options - try /usr/bin/zenemailevent --help for more details. In the $HOME of your mail user (zenoss@domain.com say), place the following (customised for your setup) in the .courier and .courier-default files: | /usr/bin/zenemailevent -u admin -p password -s http://zenoss.domain.com:8080 If you direct mail to zenoss@domain.com, it will be forwarded to your Zentinel with a default severity of info. If you send to zenoss-critical@domain.com, it'll have a Critical severity. The default event class is /Status/Update. The component and the device are calculated from the Sender/From header as component@device. As it is trivially easy to 'spoof' these, you have considerable flexibility in assuring email events are bound to their associated device(s). A real-world configuration of Monit's email alerting is as simple as (in /etc/monitrc): set mail-format { from: monit@mydevice.domain.com subject: $SERVICE $EVENT message: $ACTION: $DESCRIPTION } set alert zenoss@domain.com # Send alert to system admin on any event This will register Monit emails as info events on the /Device mydevice.domain.com. Note that because we've also removed $DATE markers from the message, monit events will roll-up.

python-zenemailevent-1.0.3-1.lbn19.noarch

If you use an MTA which can forward mail via a pipe, then you can set up mailbox(s) to collect emails and send them to your Zentinel/ZEP with this program. Here is an example using the Courier MTA and Courier Maildrop (see dot-courier and maildrop manpages in the courier-mta for further explanation), but it should work with many other forwarders. There are further options - try /usr/bin/zenemailevent --help for more details. In the $HOME of your mail user (zenoss@domain.com say), place the following (customised for your setup) in the .courier and .courier-default files: | /usr/bin/zenemailevent -u admin -p password -s http://zenoss.domain.com:8080 If you direct mail to zenoss@domain.com, it will be forwarded to your Zentinel with a default severity of info. If you send to zenoss-critical@domain.com, it'll have a Critical severity. The default event class is /Status/Update. The component and the device are calculated from the Sender/From header as component@device. As it is trivially easy to 'spoof' these, you have considerable flexibility in assuring email events are bound to their associated device(s). A real-world configuration of Monit's email alerting is as simple as (in /etc/monitrc): set mail-format { from: monit@mydevice.domain.com subject: $SERVICE $EVENT message: $ACTION: $DESCRIPTION } set alert zenoss@domain.com # Send alert to system admin on any event This will register Monit emails as info events on the /Device mydevice.domain.com. Note that because we've also removed $DATE markers from the message, monit events will roll-up.

python-ZEO-5.2.0-2.lbn25.noarch

ZEO is a client-server system for sharing a single storage among many clients. When you use ZEO, the storage is opened in the ZEO server process. Client programs connect to this process using a ZEO ClientStorage. ZEO provides a consistent view of the database to all clients. The ZEO client and server communicate using a custom RPC protocol layered on top of TCP.