Fluentd is a log collector daemon written in Ruby. Fluentd receives
logs as JSON streams, buffers them, and sends them to other systems
like MySQL, MongoDB, or even other instances of Fluentd.
This is a simple tool that dumps System V shared memory segments, files and
text. It might be useful when you have to debug programs that use System V
shared memory.
Logify is an incredibly light-weight Ruby logger with a developer-friendly API
and no dependencies. It is intentionally very opinionated and is optimized
for speed. This combination makes it perfect for command line applications.
ucspi-tcp is a set of command-line tools for building TCP-based
client/server applications. They are compliant to UCSPI, the
UNIX Client-Server Program Interface. UCSPI tools are available
for several different types of networks.
sas2ircu allows basic management of mps(4) based RAID controllers.
This includes controllers based on the LSI SAS2 IR protocol.
See the mps(4) man page for a more thorough list of controllers.
This is a set of sample XML scripts used to manage the configuration of HP
Integrated Lights-Out (iLO) management processors and to control servers in
which iLO devices are in use.
This is port of wmtop, a Windowmaker dockapp which monitors the top three
processes (in terms of CPU usage). You can configure which processes are
displayed, and it can also be used as an application launcher.
The AccountsService project provides
o A set of D-Bus interfaces for querying and manipulating
user account information.
o An implementation of these interfaces based on the usermod(8),
useradd(8) and userdel(8) commands.
cmogstored is an alternative implementation of the "mogstored" storage
component of MogileFS. cmogstored is implemented in C and does not
use Perl at runtime. cmogstored is the only component you need to
install on a MogileFS storage node.
'tbku' is a utility script for producing "tarball" backups of some- or
all of your files. It is useful both for producing incremental backups
or for systemwide images or "snapshots". The script can be run either
from the command line or, more typically, as a cron job to automate
system backup tasks.
The central benefit of using 'tbku' over hand written tar commands is
that 'tbku' is "table driven". You specify the set of files to back up
in a table (a separate file). You can have as many of these "filesets"
as you wish, corresponding to different kinds of backups you want
done. 'tbku' will do backups automatically or manually, based on the
name of the "fileset". This considerably simplifies automating
backups, keeping backup logs, and generally maintaining an orderly
backup environment.
'tbku' can also be used to capture system images which can then
later be used to (re)provision other machines.