-
python-urlgrabber-3.9.1-6.fc13.noarch
A high-level cross-protocol url-grabber for python supporting HTTP, FTP
and file locations. Features include keepalive, byte ranges, throttling,
authentication, proxies and more.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 13
-
python-virtinst-0.600.3-1.lbn13.noarch
virtinst is a module that helps build and install libvirt based virtual
machines. Currently supports KVM, QEmu and Xen virtual machines. Package
includes several command line utilities, including virt-install (build
and install new VMs) and virt-clone (clone an existing virtual machine).
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 13
-
python-volume_key-0.3.3-1.lbn13.x86_64
This package provides Python bindings for libvolume_key, a library for
manipulating storage volume encryption keys and storing them separately from
volumes.
The main goal of the software is to allow restoring access to an encrypted
hard drive if the primary user forgets the passphrase. The encryption key
back up can also be useful for extracting data after a hardware or software
failure that corrupts the header of the encrypted volume, or to access the
company data after an employee leaves abruptly.
volume_key currently supports only the LUKS volume encryption format. Support
for other formats is possible, some formats are planned for future releases.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 13
-
python-volume_key-0.3.9-2.fc18.armv6hl
This package provides Python bindings for libvolume_key, a library for
manipulating storage volume encryption keys and storing them separately from
volumes.
The main goal of the software is to allow restoring access to an encrypted
hard drive if the primary user forgets the passphrase. The encryption key
back up can also be useful for extracting data after a hardware or software
failure that corrupts the header of the encrypted volume, or to access the
company data after an employee leaves abruptly.
volume_key currently supports only the LUKS volume encryption format. Support
for other formats is possible, some formats are planned for future releases.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 13
-
python-watchdog-0.6.0-1.lbn13.noarch
Python API and shell utilities to monitor file system events.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 13
-
python-webob-1.0.8-1.lbn13.noarch
WebOb provides wrappers around the WSGI request environment, and an object to
help create WSGI responses. The objects map much of the specified behavior of
HTTP, including header parsing and accessors for other standard parts of the
environment.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 13
-
python-webtest-1.3.4-4.lbn13.noarch
WebTest wraps any WSGI application and makes it easy to send test
requests to that application, without starting up an HTTP server.
This provides convenient full-stack testing of applications written
with any WSGI-compatible framework.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 13
-
python-xlib-0.15-0.3.rc1.fc13.noarch
The Python X Library is a complete X11R6 client-side implementation,
written in pure Python. It can be used to write low-levelish X Windows
client applications in Python.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 13
-
python-xlib-doc-0.15-0.3.rc1.fc13.noarch
Install this package if you want the developers' documentation and examples
that tell you how to program with python-xlib.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 13
-
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.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 13
