-
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
-
python3-libs-3.3.0-0.3.b2.fc18.armv6hl
This package contains files used to embed Python 3 into applications.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 13
-
python3-libs-3.3.2-2.lbn13.x86_64
This package contains files used to embed Python 3 into applications.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 13
-
pywebkitgtk-1.1.8-4.fc18.armv6hl
The purpose of pywebkitgtk is to bring an alternative web engine to
Python/GTK+ application developers who might need a web browser engine for
their next application or developers wishing to have a better browser engine
that they can access to using the Python programming language.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 13
-
pywebkitgtk-1.1.8-5.lbn13.x86_64
The purpose of pywebkitgtk is to bring an alternative web engine to
Python/GTK+ application developers who might need a web browser engine for
their next application or developers wishing to have a better browser engine
that they can access to using the Python programming language.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 13
-
pyxdg-0.17-1.fc12.noarch
PyXDG is a python library to access freedesktop.org standards
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 13
-
pyxf86config-0.3.37-7.fc12.x86_64
Python wrappers for the X server config file library libxf86config.
It is used to read and write X server configuration files.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 13
-
qca2-2.0.2-2.fc12.x86_64
Taking a hint from the similarly-named Java Cryptography Architecture,
QCA aims to provide a straightforward and cross-platform crypto API,
using Qt datatypes and conventions. QCA separates the API from the
implementation, using plugins known as Providers. The advantage of this
model is to allow applications to avoid linking to or explicitly depending
on any particular cryptographic library. This allows one to easily change
or upgrade crypto implementations without even needing to recompile the
application!
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 13
-
qca2-2.0.3-4.fc18.armv6hl
Taking a hint from the similarly-named Java Cryptography Architecture,
QCA aims to provide a straightforward and cross-platform crypto API,
using Qt datatypes and conventions. QCA separates the API from the
implementation, using plugins known as Providers. The advantage of this
model is to allow applications to avoid linking to or explicitly depending
on any particular cryptographic library. This allows one to easily change
or upgrade crypto implementations without even needing to recompile the
application!
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 13
