The Middleman System (mdm) is a set of utilities that help you parallelize your shell scripts. Its design is based on ideas from superscalar computer processors: it fetches commands as your script is running, detects potential interference between commands on the fly, and issues commands for execution in parallel as appropriate.
LMDBG is a collection of small tools for collecting and analyzing the logs of malloc/realloc/memalign/free function calls. Unlike many others, LMDBG does not provide any way to detect overruns of the boundaries of malloc() memory allocations, as this is not the goal. Like most other malloc debuggers, LMDBG allows detecting memory leaks and double frees. However, unlike others, LMDBG generates full stacktraces and separates the logging process from analysis, thus allowing you to analyze an application on a per-module basis.
depfinder finds the dependencies of Slackware packages. The dependency list can be output to stdout, to a .dep text file without version information, or to a slack-required file with version information. depfinder is very fast; its speed is mainly due to the C++ code that is used in depfinder to find in which package each individual library is included. It also has support for running multiple jobs, which makes it a lot faster when used with multiple CPUs/cores. depfinder supports detecting dependencies of binary files compiled with languages such as C or C++ and it can also detect Python dependencies.
LPAR2RRD makes historical, future trends and nearly "realtime" CPU utilization graphs of LPARs and shared CPU usage of IBM Power servers. It collects complete physical and logical configuration of all servers/LPARs. It is agent-less (it gets everything from the HMC/SDMC or IVM). It supports all kinds of logical partitions (AIX/AS400/Linux/VIOS).
Cloud User Shell (cush) is a multi-call executable bringing RESTful cloud control to the command line, combining many useful cloud computing utilities into a single executable. It follows the Unix philosophy of writing components that work together, do one thing and do it well, and communicate over text (HTTP) streams. It is also RESTful, clearly delineating the 3 sides of the REST Triangle: verbs (e.g. GET), nouns (e.g. http://samj.net/), and content types (e.g. text/html).