nxlog is a modular, multi-threaded, high-performance log management solution with multi-platform support. In concept, it is similar to syslog-ng or rsyslog, but is not limited to Unix/syslog only. It can collect logs from files in various formats, receive logs from the network remotely over UDP, TCP, or TLS/SSL on all supported platforms. It supports platform-specific sources such as the Windows Eventlog, Linux kernel logs, Android device logs, local syslog, etc. Writing and reading logs to/from databases is also supported for many database servers. The collected logs can be stored into files, databases, or forwarded to a remote log server using various protocols. The old BSD Syslog and the newer IETF syslog standard (RFC 3164 and RFC 5424-5426) are fully supported by nxlog in addition to XML, JSON, CSV, GELF, and other custom formats. A key concept in nxlog is to be able to handle and preserve structured logs so there is no need to convert everything to syslog and then parse these logs again at the other side. It has powerful message filtering, log rewrite, and conversion capabilities. Using a lightweight, modular, and multi-threaded architecture which can scale, nxlog can process hundreds of thousands of events per second.
Fossil is a distributed software configuration management/version control system built with reliability and ease of use on mind. It comes with integrated bug tracking and a wiki. It is distributed as a single static binary for easy installation and the ability to run in a chrooted environment. Other highlights include a Web interface, autosync, simple networking, and CGI support.
Class::EHierarchy is intended for use as a base class for custom objects. The objects need one or more of the following features: orderly bottom-up destruction of objects, opaque objects, class-based access restrictions for properties and methods, primitive strict property type awareness, and alias-based object retrieval.