torture is a suite of programs designed to torture specific either
specific parts or the system as a whole.
torture and port by thib, with tweaks from armani@
ok armani@
In the upgrade from ruby 1.8.6 to 1.8.7, the PLISTs changed
due to differences in how RDoc processes files.
This also has a number of changes to the regress tests to
work with the changes to devel/ruby-rake. It moves most of
the regress tests to use MODRUBY_REGRESS.
OK jcs@, landry@, jasper@, sthen@
The System Tools Backends (s-t-b for short) are a set of cross-platform
modules for Unix systems. The backends provide a common DBus interface
to all platforms to modify or read the system configuration in a system
independent fashion. Historically, access to system configuration has
<...>
This is a WIP, hence not hooked to the build.
DO NOT try this at home or you will harm yourself, you have been warned.
ok jasper@
subpackage, same version. It makes very little sense to only install a
plugin.. bump corresponding REVISIONs.
With tweaks from sthen@, agreed by espie@
Rsyslog is an enhanced multi-threaded syslogd with a focus on
security and reliability. Among others, it offers support for
on-demand disk buffering, reliable syslog over TCP, SSL, TLS and
RELP, writing to databases (MySQL, PostgreSQL, Oracle, and many
more), email alerting, fully configurable output formats (including
high-precision timestamps), the ability to filter on any part of
the syslog message, on-the-wire message compression, and the ability
to convert text files to syslog. It is a drop-in replacement for
stock syslogd and able to work with the same configuration file
syntax. Its advanced features make it suitable for enterprise-class,
encryption protected syslog relay chains while at the same time
being very easy to setup for the novice user.
initial port from todd@, improved by sthen@ and me
librelp is an implementation of RELP, Reliable Event Logging Protocol.
RELP assures that no message is lost, not even when connections break
and a peer becomes unavailable.
The current version of RELP has a minimal window of opportunity for
message duplication after a session has been broken due to network
problems. In this case, a few messages may be duplicated (a problem
that also exists with plain tcp syslog). Future versions of RELP
will address this shortcoming.
feedback from stuart and steven m.
- install a better sample config file, which mimics OpenBSD's syslogd
and no longer spits all kinds of warnings just because we are using
syslog-ng >= 3
this allows to start syslog-ng without extra arguments and have something
basically working.
requested by jcs@
let me know if you find issues with the new config file.
