Monit is a utility for managing and monitoring processes, programs, files, directories, and devices on a Unix system. It conducts automatic maintenance and repair and can execute meaningful causal actions in error situations. It can be used to monitor files, directories, and devices for changes, such as timestamps changes, checksum changes, or size changes. It is controlled via an easy to configure control file based on a free-format, token-oriented syntax. It logs to syslog or to its own log file and notifies users about error conditions via customizable alert messages. It can perform various TCP/IP network checks, protocol checks, and can utilize SSL for such checks. It provides an HTTP(S) interface for access.
Zild is a C application server with support for the common servlet technology and servlet API in C. It includes support for ServerPages, PHP, XML SAX parser, HTTP/1.1 and SSL/TLS connectors, HTML form-based and Basic Authentication access controls, a built-in embedded SQL database, and many more functions.
Libzdb is a database library with thread-safe connection pooling. The library can connect transparently to multiple database systems. It has zero runtime configuration and connections are specified via a URL scheme. A modern object-oriented API is provided. Libzdb supports MySQL, PostgreSQL, SQLite, and Oracle.
Missing concepts and tools
At least two important concepts are missing with regards to build management:
Completeness; That the correct versions of all components are built into a release and Consistence; that the whole system is build with all components. That the author forget to mention the make tool but instead focus on Perl is strange. Make provides a dependency graph of components which is important for consistent builds and make also provide a much better tool for completeness and automatic build than Perl.
I also find it strange that the authorís descriptions of release management donít mention Version control and Change control. For version control, CVS is probably the common single most used tool in the OSS community and should have been mentioned. And Bugzilla is a good example for change control.