Moscrack is a WPA cracker for use on clusters. It supports MOSIX, SSH, and RSH connectivity and works by reading a word list from STDIN or a file, breaking it into chunks, and passing those chunks off to separate processes that run in parallel. The parallel processes are then executed on different nodes in your cluster. All results are checked and recorded on your master node. Logging and error handling are taken care of. It is capable of running reliably for long periods of time, without the risk of losing data or having to restart. Moscrack uses aircrack-ng by default. Pyrit for WPA cracking and Dehasher for Unix password hashes are supported via plugins.
Osgish is a command line shell for OSGi. It is based on the Readline Library, Jmx4Perl, as the OSGi backend, and Aries JMX as the OSGi Management layer. It is different than other OSGi shells, as it is implemented in pure Perl and provides unique features like wildcard support, context-sensitive command line completion, syntax highlighting, bulk lifecycle operations, advanced query facilities, and remoting via HTTP. It uses jmx4perl and Aries JMX OSGi bundles for accessing the OSGi container remotely.
FusionInventory Agent is an generic inventory agent that can collect information from various sources including the local machine, network, and remote devices. It also has the ability to send Wake on LAN requests and deploy software. The agent can be used with GLPI, Uranos, Rudder, Pulse2, and OCS Inventory.
OCS Inventory is an application designed to help a network or system administrator keep track of the configuration and software of computers that are installed on the network. Information about hardware and operating system are collected. OCS Inventory is also able to detect all active devices on your network, such as switches, routers, network printers, and unattended devices. It also allows you to deploy software, commands, or files on client computers.
Schedule::Cron is a Perl module that provides a simple but complete cron-like scheduler. It can be used for periodically executing Perl subroutines. The philosophy behind Schedule::Cron is to call subroutines periodically from within one single Perl program instead of letting cron trigger several (possibly different) Perl scripts. Everything under one roof. Furthermore, Schedule::Cron provides a mechanism to create crontab entries dynamically, which isn't that easy with cron. It knows about all extensions (at least all extensions the author is aware of, i.e those of "Vixie" cron) for crontab entries like ranges including 'steps', specification of month and days of the week by name, or coexistence of lists and ranges in the same field. It even supports a bit more (like lists and ranges with symbolic names). It has existed since 1999 on CPAN and is successfully used in many projects.