The Network Time Protocol (NTP) is used to synchronize the time of a computer client or server to another server or reference time source, such as a radio or satellite receiver or modem. It provides client accuracies typically within a millisecond on LANs and up to a few tens of milliseconds on WANs relative to a primary server synchronized to Coordinated Universal Time (UTC) via a Global Positioning Service (GPS) receiver, for example.
Enterprise Audit Shell (EAS) allows organizations to centrally audit and report UNIX shell access. Unlike Sudosh, the audit logs are sent to a centralized archive and reporting server. Client server authentication and encryption is handled by SSL. It was specifically designed for enterprise, commercial use.
Daikon is an implementation of dynamic detection of likely invariants. An invariant is a property (such as "x=2*y+5" or "this.next.prev = this" or "myarray is sorted by <") that holds at a certain point or points in a program. Invariants are often seen in assert statements, documentation, and formal specifications. Invariants can be useful in program understanding and a host of other applications. Daikon runs a program, observes the values that the program computes, and then reports properties that were true over the observed executions. It can detect properties in Java, C, C++, Perl, and IOA programs, in spreadsheet files, and in other data sources.
LFT (Layer Four Traceroute) is a sort of "traceroute" that often works much faster than the commonly-used Van Jacobson method and goes through many configurations of packet-filter based firewalls. More importantly, LFT implements numerous other features, including TCP, UDP, or ICMP-based traces, AS number lookups through several reliable sources, loose source routing, netblock name lookups, and more. LFT also distinguishes between layer-4 protocols, which make its statistics slightly more realistic, and gives a savvy user the ability to trace protocol routes, not just layer-3 hops.
ZMailer is an internet message transfer agent. It is intended for gateways or mail servers or other large site environments that have extreme demands on the abilities of the mailer. It was motivated by the problems of the Sendmail design in such situations. It is intended and designed as a multi-protocol mailer. The only protocol supported in this distribution is RFC822 (and variations).
nmdb is a network database (dbm-style) that can use multiple protocols to communicate with its clients. TIPC, TCP, UDP, and SCTP are currently supported. It consists of an in-memory cache that saves (key, value) pairs, and a persistent backend that stores the pairs on disk. Both work in combination, but the use of the backend is optional, so you can use the server only for cache queries, pretty much like memcached.