* cfgen, a config files generator that is fed with config templates and
parameters to fill them
* CronBuilder, to pull a repository, run building command, and save the
results in another repository
* flowmon, which shows bandwith usage of different streams, each defined by
BPF filter (a.k.a. "tcpdump syntax")
* sftponly, a shell for jailing in chroot accounts meant for data transfer
only (for scp, sFTP, and rsync)
* xmlrpcd and its spiritual successor HarpCaller, RPC daemons for sysadmins
* logdevourer, log parsing daemon
These are just the public ones, the ones that were generic enough to be open
sourced. I have few others that are/were too specific to the environment they
were written for.
And with packages, I disagree. I only use Debian (and have used Red Hat some
time ago), so it would be quite troublesome for me to provide package build
scripts for anything else. I wouldn't expect any developer to provide
packaging for the whole variety of distributions and OSes. But providing
a sane build process is enough for anybody to build a package for their OS.
* cfgen, a config files generator that is fed with config templates and parameters to fill them
* CronBuilder, to pull a repository, run building command, and save the results in another repository
* flowmon, which shows bandwith usage of different streams, each defined by BPF filter (a.k.a. "tcpdump syntax")
* sftponly, a shell for jailing in chroot accounts meant for data transfer only (for scp, sFTP, and rsync)
* xmlrpcd and its spiritual successor HarpCaller, RPC daemons for sysadmins
* logdevourer, log parsing daemon
These are just the public ones, the ones that were generic enough to be open sourced. I have few others that are/were too specific to the environment they were written for.