cvs-fast-export analyzes a collection of RCS files in a CVS repository (or outside of one) and, when possible, emits an equivalent history in the form of a fast-import stream. Not all possible histories can be rendered this way; the program tries to emit useful warnings when it can't. The program can also produce a visualization of the resulting commit DAG in the DOT format handled by the graphviz suite. The package also includes cvssync, a tool for mirroring masters from remote CVS hosts.
cronbot is a wrapper script for cron jobs. Rather than running your job/script directly, you run it through cronbot, and it will allow a little more control to help keep things from getting out of hand. The default behavior is to only allow one instance of your job to run. This can be changed with the --duplicate option. You can also pass in a maximum time of execution for a job or add a random amount time to delay the start of your job. By default, jobs are run with a default "nice" value, which is usually 10.
pyReScene is a tool that recreates original RARs by backing up the metadata. It is a port of ReScene .NET to Python. It provides a mechanism for backing up and restoring the metadata from "scene" released RAR files. RAR archive volumes are rebuilt using the stored metadata in the SRR file and the files extracted from the RAR archive. pyReScene consists of multiple related tools: pyReScene Auto to create a complete SRR with one simple command, pyReSample to recreate sample files, and pyReScene Usenet to create SRR files on the fly from Usenet postings. Lots of other small scripts for managing SRR and SRS files are available too.
check_nwc_health is a plugin for the Shinken (or Nagios/Icinga) monitoring system. It is used to check hardware health, environment, interfaces, pools, uptime, etc. of a great range of the most popular network components like switches, routers, firewalls, proxies, load balancers, etc. Currently it can monitor: Cisco IOS, Cisco Nexus, F5 BIG-IP, CheckPoint Firewall1, Juniper NetScreen, HP Procurve, Nortel, Brocade 4100/4900, EMC DS 4700, EMC DS 24, Allied Telesyn, and Blue Coat SG600.
Flawless traps exceptions and then uses git blame to send an email to the developer who wrote the buggy code. Even if a particular line of code causes thousands of exceptions, only one email will be sent. It uses git-blame to figure out which developer is responsible for a particular exception, and will only email that developer. If you set report_only_after_minimum_date, then Flawless will only report exceptions caused by code modified after report_only_after_minimum_date. You can mark certain files/functions as library code, and when an exception originates in those files/functions, the caller will be blamed for the error instead of the library code.