Pandora FMS is a monitoring Open Source software. It watches your systems and
applications, and allows you to know the status of any element of those systems.
Pandora FMS could detect a network interface down, a defacement in your
website, a memory leak in one of your server application, or the movement of
any value of the NASDAQ new technology market. Pandora FMS could send out SMS
message when your systems fails... or when Google's value drop below US348.60?
Pandora FMS runs on any operating system, with specific agents for each
platform, gathering data and sending it to a server, it has specific agents for
GNU/Linux, AIX, Solaris, HP-UX, BSD/IPSO, and Windows 2000, XP and 2003.
Pandora FMS can also monitor any kind of TCP/IP service, without the need to
install agents, and monitor network systems such as load balancers, routers,
switches, operating systems, applications, or simply printers if you need.
Pandora FMS also supports SNMP for collecting data and for receiving traps.
A few examples of common resources monitored by Pandora FMS could be processor
load, disk and memory usage, running processes, log files, environmental
factors such as temperature, or application values like strings contained in
web pages or any possible way to collect data in an automatic way.
With the exponential growth of the Internet, a central Whois database that
provides host and network information of systems connected to the Internet,
and electronic mail (email) addresses of the users of those systems has
proven to be very inefficient. The sheer size and effort needed to maintain
a centralized database necessitates an alternate, decentralized approach to
storing and retrieving this information.
RWhois is a Directory Services protocol which extends and enhances the Whois
concept in a hierarchical and scaleable fashion. It focuses on the
distribution of "network objects"--the data representing Internet resources
or people--and uses the inherently hierarchical nature of these network
objects (domain names, Internet Protocol (IP) networks, email addresses) to
more accurately discover the requested information.
RWhois synthesizes concepts from other, established Internet protocols to
create a more useful way to find resources across the Internet. The RWhois
protocol and architecture derive a great deal of structure from the Domain
Name System (DNS) [RFC 1034] and borrow directory service concepts from
other directory service efforts, primarily [X.500]. The protocol is also
influenced by earlier established Internet protocols, such as the Simple
Mail Transport Protocol (SMTP) [RFC 821] for response codes.
OpenPGM is an open source implementation of the Pragmatic General Multicast
(PGM) specification in RFC 3208 available at www.ietf.org. PGM is a reliable
and scalable multicast protocol that enables receivers to detect loss, request
retransmission of lost data, or notify an application of unrecoverable loss.
PGM is a receiver-reliable protocol, which means the receiver is responsible
for ensuring all data is received, absolving the sender of reception
responsibility. PGM runs over a best effort datagram service, currently OpenPGM
uses IP multicast but could be implemented above switched fabrics such as
InfiniBand.
PGM is appropriate for applications that require duplicate-free multicast data
delivery from multiple sources to multiple receivers. PGM does not support
acknowledged delivery, nor does it guarantee ordering of packets from multiple
senders.
PGM is primarly used on internal networks to help integrate disparate systems
through a common communication platform. A lack of IPv4 multicast-enabled
infrastructure leads to limited capability for internet applications, IPv6
promotes multicast to be a part of the core functionality of IP but may still
be disabled on core routers. Support of Source-Specific Multicast (SSM) allows
for improved WAN deployment by allowing end-point router filtering of unwanted
source traffic
AUC TeX is a comprehensive customizable integrated environment for
writing input files for LaTeX using GNU Emacs.
AUC TeX lets you run TeX/LaTeX and other LaTeX-related tools, such
as a output filters or post processor from inside Emacs. Especially
`running LaTeX' is interesting, as AUC TeX lets you browse through the
errors TeX reported, while it moves the cursor directly to the reported
error, and displays some documentation for that particular error. This
will even work when the document is spread over several files.
AUC TeX automatically indents your `LaTeX-source', not only as you
write it -- you can also let it indent and format an entire document.
It has a special outline feature, which can greatly help you `getting an
overview' of a document.
Apart from these special features, AUC TeX provides a large range of
handy Emacs macros, which in several different ways can help you write
your LaTeX documents fast and painlessly.
All features of AUC TeX are documented using the GNU Emacs online
documentation system. That is, documentation for any command is just
a key click away! AUC TeX is written entirely in Emacs-Lisp, and hence
you can easily add new features for your own needs.
XMakemol is a program written for UN*X operating systems in ANSI C using the X,
Xt and Motif libraries. It can be used to view and manipulate atomic and
molecular data given in xyz format.
XMakemol is a mouse-based application and many features can be accessed by
clicking or dragging the mouse on the main window. Additional popup dialogs
offer a number of additional features.
Here is what an XMakemol session might look like. The system is a bucky ball
and the Measure dialog is showing the measurement of bond-lengths, angles and
a torsion angle.
XMakemol can produce output in PostScript (black and white or colour)and in xpm
format (which can be translated to gif format using xpmtoppm and ppmtogif).
XMakemol can also produce a series of xpm files which can be translated into an
animated gif file using the bundled utility xmake_anim.pl (formerly
gmake_anim.pl). The one above is an animation of the "viagra" molecule
(sidenafil).
Barnyard is a critical tool for the parsing of Snort's unified binary files,
processing and on-forwarding to a variety of output plugins. Unfortunately
it has not seen an updated in over 4 years and is not going to be maintained
by the original developers. With the new version of the unified format
(ie. unified2) arriving we need something to bridge this gap.
The SXL team love barnyard. So much so that we want it to stay and have been
tinkering around with the code to give it a breath of new life. Here is what
we have achieved to far for this reinvigorated code base:
* Parsing of the new unified2 log files.
* Maintaining majority of the command syntax of barnyard.
* Addressed all associated bug reports and feature requests arising since
barnyard-0.2.0.
* Completely rewritten code based on the GPLv2 Snort making it entirely
GPLv2.
This is an effort to fuse the awesome work of Snort and the original concept
of barnyard giving it a fresh update along the way. We've come a long way so
far and have a very stable build that we've integrated into our NSMnow
framework. If you have any feature requests, bugs or gripes then send them
our way.
CryptoFS is a encrypted filesystem for Filesystem in Userspace (FUSE) and
the Linux Userland FileSystem (LUFS). Visit http://fuse.sourceforge.net/
for more information on FUSE, or http://lufs.sourceforge.net/lufs/ for
more information on LUFS.
CryptoFS will use a normal directory to store files encrypted. The
mountpoint will contain the decrypted files. Every file stored in this
mountpoint will be written encrypted (data and filename) to the directory
that was mounted. If you unmount the directory the encrypted data can only
be access by mounting the directory with the correct key again. Like other
FUSE/LUFS filesystems it does not need root access or any complicated setup
like creating a filesystem on a encrypted disk using the loop device.
CryptoFS can be build for FUSE, and LUFS. When you build for FUSE you get
a program to mount the filesystem. For LUFS a shared library will be built
that can be used by LUFS's lufsd. Both methods can use the same encrypted
directory.
Data::FormValidator's main aim is to make the tedious coding of input
validation expressible in a simple format and to let the programmer focus
on more interesting tasks.
When you are coding a web application one of the most tedious though
crucial tasks is to validate user's input (usually submitted by way of
an HTML form). You have to check that each required fields is present
and that some fields have valid data. (Does the phone input looks like a
phone number? Is that a plausible email address? Is the YY state
valid? etc.) For a simple form, this is not really a problem but as
forms get more complex and you code more of them this task becames
really boring and tedious.
Data::FormValidator lets you define profiles which declare the
required fields and their format. When you are ready to validate the
user's input, you tell Data::FormValidator the profile to apply to the
user data and you get the valid fields, the name of the fields which
are missing. An array is returned listing which fields are valid,
missing, invalid and unknown in this profile.
Seamus Venasse <svenasse@polaris.ca>
This module exports two functions, nsort and ncmp; they are used in implementing
my idea of a "natural sorting" algorithm. Under natural sorting, numeric
substrings are compared numerically, and other word-characters are compared
lexically.
This is the way I define natural sorting:
* Non-numeric word-character substrings are sorted lexically,
case-insensitively: "Foo" comes between "fish" and "fowl".
* Numeric substrings are sorted numerically: "100" comes after "20",
not before.
* \W substrings (neither words-characters nor digits) are ignored. Our use
* of \w, \d, \D, and \W is locale-sensitive: Sort::Naturally
uses a use locale statement.
* When comparing two strings, where a numeric substring in one place
is not up against a numeric substring in another, the non-numeric always comes
first. This is fudged by reading pretending that the lack of a number substring
has the value -1, like so:
* The start of a string is exceptional: leading non-\W (non-word,
non-digit) components are ignored, and numbers come before letters.
* I define "numeric substring" just as sequences matching m/\d+/ --
scientific notation, commas, decimals, etc., are not seen. If your data has
thousands separators in numbers ("20,000 Leagues Under The Sea" or "20.000
lieues sous les mers"), consider stripping them before feeding them to nsort or
ncmp.
Kwiki - The Kwiki Wiki Building Framework
A Wiki is a website that allows its users to add pages, and edit any
existing pages. It is one of the most popular forms of web
collaboration. If you are new to wiki, visit
http://c2.com/cgi/wiki?WelcomeVisitors which is possibly the oldest
wiki, and has lots of information about how wikis work.
Kwiki is a Perl wiki implementation based on the Spoon application
architecture and using the Spiffy object orientation model. The major
goals of Kwiki are that it be easy to install, maintain and extend.
All the features of a Kwiki wiki come from plugin modules. The base
installation comes with the bare minimum plugins to make a working
Kwiki. To make a really nice Kwiki installation you need to install
additional plugins. Which plugins you pick is entirely up to you.
Another goal of Kwiki is that every installation will be unique. When
there are hundreds of plugins available, this will hopefully be the
case.