Free tc config software for linux

tc_config provides a set of scripts for Linux traffic control.

tc_config is set of scripts for Linux 2.4+ traffic control configuration on Red Hat systems and (hopefully) derivatives. It uses cbq qdisc as root one, and sfq qdisc at the leaves.

It includes the snmp_pass utility for getting stats on traffic control via SNMP.

Run: rpm -tb tc-config-0.6.tar.gz (rmpbuild on redhat 8+ systems).

After package will be built, run
rpm -Uvh /usr/src/redhat/RPMS/i386/tc-config-0.6-1.i386.rpm.

DOCSIS Config provides a PHP library to encode binary configuration files for DOCSIS cable modems.

Snort Config provides an intuitive menu-based interface for the GPL IDS tool Snort.
SnortConf is a tool that provides a fairly intuitive menu-based text interface for setting up the GPL IDS tool Snort. It also provides error and sanity checking on user input, and an online help facility.
Currently, Ive just released a Snortconf version to match up to Snort version 1.9.0. I apologize for the late release date; this project is a unique one for me, in that I dont use this program myself (I like the text editor method better personally), so I tend to forget about it if nobody pesters me, which nobody has. Speaking of which:
NOTE TO USERS: If you like this program, or hate this program, or anything else about this program (feature requests? bugs?), please provide me some feedback. My purpose in releasing this program in its current BETA state was to get feedback from people who use it, and to date I have gotten exactly 1 person willing to drop me an e-mail on the subject. The rest of you are encouraged to join in.
The program should compile on almost any POSIX system with a Curses library. It has only been tested on Linux/Ncurses however, so users of other platforms are encouraged to report any issues they encounter with either the build process, or any runtime errors.
Enhancements:
- yncd to changed on the debian boxen.
- rebuilt RPM and tar.gz on the RedHat boxen.
- Updated to output Snort 1.9.0 config files.
- Dang little else. :)

MRTG::Config is a Perl module for parsing MRTG configuration files.

WARNING

This module, while reliable right now, is still in ALPHA stages of development... The API/methods may change. Behaviors of methods will almost certainly change. The internal structure of data will change, as will many other things.

I will try to always release working versions, but anyone who expects their code that uses this module to continue working shouldnt... until I remove this warning.

SYNOPSIS

Ever have the need to parse an MRTG config file? I have. I needed to parse lots and lots of them. Using the functions built-in to MRTG_lib was too slow, too complex, and used too much RAM and CPU time for my poor web server to handle - and the data structures MRTG_lib built were way more complex than I needed.

MRTG::Config can load and parse MRTG and MRTG-style confiuguration files very quickly, and the parsed directives, targets and values can be located, extracted, and manipulated through an OO interface.

This module is intended to focus on correctly parsing the format of an MRTG configuration, regardless of whether or not the directives and values, etc. are valid for MRTG. I am using both the parsing behavior of MRTG_libs readcfg() function and the description of the format on the MRTG website as my guidelines on how to correctly parse these configuration files. I am still a short way off that goal, but this module is currently being used in a production environment with great success!

PLEA FOR MERCY

I plan on adding to this documentation and making it better organized soon, but Im willing to answer questions directly in the mean time. Also, this is my first module, written in a hurry to appease some disgruntled engineers. I do plan on continuing to improve it, so any input, positive or negative is certainly welcome!

USAGE EXAMPLE

use MRTG::Config;

my $cfgFile = mrtg.cfg;
my $persist_file = mrtg.cfg.db;

my $mrtgCfg = new MRTG::Config;

$mrtgCfg->loadparse($cfgFile);

# Want to store the parsed data for use later or by
# another program?
$mrtgCfg->persist_file($persist_file);
$mrtgCfg->persist(1);

foreach my $tgtName (@{$mrtgCfg->targets()}) {
my $tgtCfg = $mrtgCfg->target($tgtName);
# Lets assume every target has a Title.
print $tgtCfg->{title} . "n";
}

# globals() has some, um, interesting things you
# should know. Please read about it below...
my $globalCfg = $mrtgCfg->globals();

# Lets assume WorkDir is set.
print $globalCfg->{workdir} . "n";

Rsync::Config is a Perl module for rsync configuration generator.

Rsync::Config is a module who can be used to create rsync configuration files. A configuration file (from Rsync::Config point of view) is made by atoms and modules with atoms. A atom is the smallest piece from the configuration file. This module inherits from Rsync::Config::Module .

INHERITANCE

Objects from Rsync::Config inherits as in the next scheme

/--- Rsync::Config::Module --- Rsync::Config

Rsync::Config::Renderer

--- Rsync::Config::Blank
/

Rsync::Config::Atom --- --- Rsync::Config::Comment

SYNOPSIS

use Rsync::Config;
use Rsync::Config::Atom;
use Rsync::Config::Module;

sub main {
my ($conf, $module);

$conf = new Rsync::Config();
$conf->add_comment(Main configuration file for our rsync daemon);
$conf->add_atom(read only,yes);
$conf->add_atom(chroot,yes);

$module = new Rsync::Config::Module(name => cpan);
$module->add_atom(path,/var/ftp/pub/mirrors/ftp.cpan.org/);
$module->add_atom(comment, CPAN mirror);

$conf->add_module($module);
$conf->to_file(/etc/rsyncd.conf);
}

Config::YUM is a Perl extension for parsing yum.conf.

SYNOPSIS

use Config::YUM;

my $yp = new Config::YUM;
my $yum_conf = $yp->parse();

foreach(keys %{$yum_conf}) {
print "Section: $_ is called " . $yum_conf->{$_}->{name} . "n";
}

$yum_conf will be a a hash, all INI sections are the primary hash keys.
include= will be automatically downloaded merged with the local yum.conf
mirrorlists will also be downloaded and saved as an array in $yum_conf->{somerepo}->{baseurls}
the first url in mirrorlists will be safed as $yum_conf->{somerepo}->{baseurl}.
exclude statements will be splited and safed to $yum_conf->{somerepo}->{exclude_hash}. Note that we
safe a perl regex string as keys here.

To say it with one sentence. Config::YUM automatically parses a yum.conf does the downloading and provides you
with a ready to use perl hash. :-)

You can define a few things @ new:

- use_cache: 0/1 (1 will enable, default: 0; Uses Cache::File)

- yum_conf: path to your yum.conf (default: /etc/yum.conf)

- yum_repos_d: path to your yum.repos.d (default: /etc/yum.repos.d)

- agent: You LWP::UserAgent agent string (default: Config::YUM/$VERSION)

- releasever: Define your RH/FC release version (rpm -qf --queryformat %{VERSION} /etc/redhat-release; Default: automatically queried)

- basearch: Define your basearch (uname -i; Default: automatically discovered)

- download_primary: Define if we should download/parse the primary.xml.gz

These arguments can be specified this way (dont forget the {!)
my $yp = new Config::YUM({
use_cache => 1,
yum_conf => /etc/yum.conf,
yum_repos_d => /etc/yum.repos.d,
agent => MyProgram/$VERSION,
relasever => 4,
basearch => i386,
download_primary => 1
});

This module provides you with a few functions,
parse() will return a hash containing the allready parsed local/remote yum.conf.

yumconf_local() will return a hash containing the allready parsed local yum.conf (Will run parse(), if you didnt yet)
yumconf_remote() will return a hash containing the allready parsed remote yum.conf (Will run parse(), if you didnt yet)

Nagios Config project is a Web-based front end for configuring Nagios 1.x.
Nagios is a host and service monitor designed to inform you of network problems before your clients, end-users or managers do. It has been designed to run under the Linux operating system, but works fine under most *NIX variants as well.
The monitoring daemon runs intermittent checks on hosts and services you specify using external "plugins" which return status information to Nagios. When problems are encountered, the daemon can send notifications out to administrative contacts in a variety of different ways (email, instant message, SMS, etc.). Current status information, historical logs, and reports can all be accessed via a web browser.
Main features:
- Monitoring of network services (SMTP, POP3, HTTP, NNTP, PING, etc.)
- Monitoring of host resources (processor load, disk and memory usage, running processes, log files, etc.)
- Monitoring of environmental factors such as temperature
- Simple plugin design that allows users to easily develop their own host and service checks
- Ability to define network host hierarchy, allowing detection of and distinction between hosts that are down and those that are unreachable
- Contact notifications when service or host problems occur and get resolved (via email, pager, or other user-defined method)
- Optional escalation of host and service notifications to different contact groups
- Ability to define event handlers to be run during service or host events for proactive problem resolution
- Support for implementing redundant and distributed monitoring servers
- External command interface that allows on-the-fly modifications to be made to the monitoring and notification behavior through the use of event handlers, the web interface, and third-party applications
- Retention of host and service status across program restarts
- Scheduled downtime for suppressing host and service notifications during periods of planned outages
- Ability to acknowledge problems via the web interface
- Web interface for viewing current network status, notification and problem history, log file, etc.
- Simple authorization scheme that allows you restrict what users can see and do from the web interface
Enhancements:
- A require_once() statement in cleardb_import.php was fixed.
- The main page was redesigned to be more efficient.
- A problem in services_A1.php was fixed.

Config::Sofu is a simple Sofu configuration file parser.

SYNOPSIS

use vars qw/%CONFIG/;
use Config::Sofu "config.sofu";
if ($CONFIG{FOOBAR}) {
...
}
if ($CONFIG{Bar}->[7]->{Foo} eq "Foobar") {
...
}
Save the new configuration:
$CONFIG{FOOBAR}="Bar times Foo";
Config::Sofu::save;
or
Config::Sofu::save(%CompletlyNewConfig)

SYNTAX

This class exports the hash %CONFIG by default which contains all the information of the file which is given to the use statement.