Free configfile software for linux

App::Conf::File is a Perl module to load and access configuration data.

SYNOPSIS

use App::Conf;

$config = App::Conf->new();
$config = App::Conf->new(configFile => $file);
print $config->dump(), "n"; # use Data::Dumper to spit out the Perl representation

# accessors
$property_value = $config->get($property_name);
$branch = $config->get_branch($branch_name); # get hashref of properties

# on-demand loading helper methods (private methods)
$config->overlay($config2); # merge the two config structures using overlay rules
$config->overlay($config1, $config2); # merge $config2 onto $config1
$config->graft($branch_name, $config2); # graft new config structure onto branch

# By convention, the configurations for each App-Context service will be located
# two levels under the hash ref as shown.

$config->{Conf} # config settings for all Conf services
$config->{Conf}{default} # config settings for the default Conf service
$config->{Security} # config settings for all Security services
$config->{Security}{default} # config settings for the default Security service
$config->{Template}{tt} # config settings for the Template service named "tt"

# The default driver (if "configClass" not supplied) reads in a Perl
# data structure from the file. Alternate drivers can read a Storable,
# unvalidated XML, DTD-validated XML, RDF-validated XML, or any other
# file format or data source anyone cares to write a driver for.

$conf = {
Standard => {
Log-Dispatch => {
logdir => /var/p5ee,
}
},
Authen => {
passwd => /etc/passwd,
seed => 303292,
},
};

# A comparable unvalidating XML file would look like this.

< conf>
< Standard>
< Log-Dispatch logdir="/var/p5ee"/>
< /Standard>
< Authen passwd="/etc/passwd" seed="303292"/>
< /conf>

# A comparable ini file (.ini) would look like this.

[Standard.Log-Dispatch]
logdir = /var/p5ee
[Authen]
passwd = /etc/passwd
seed = 303292

# A comparable Java properties-like file would look like this.

Standard.Log-Dispatch.logdir = /var/p5ee
Authen.passwd = /etc/passwd
Authen.seed = 303292

GO::View is a Perl module that creates a gif or png image for visualizing the GO DAG.

This perl module generates a graphic that displays the parent and child relationships of a selected GO term. It also provides the visualization for the GO::TermFinder perl module created by the Stanford Microarray Database (SMD). This module is useful when analyzing experimental or computational results that produce a set of gene products that may have a common function or process.

SYNOPSIS

use GO::View;

my $goView =

GO::View->new(-goid => $goid,
-ontologyProvider => $ontology,
-annotationProvider => $annotation,
-termFinder => @pvalues,
-aspect => P,
-configFile => $confFile,
-imageDir => "/tmp",
-imageUrlRoot => "http://www.ABC.com/tmp",
-imageName => "GOview.88.png",
-tree => up,
-nodeUrl => $goUrl,
-geneUrl => $geneUrl,
-pvalueCutOff => 0.01,
-imageLabel => "SGD");


argument required expect data and type
-------------------------------------------------------------------------
-goid No A gene ontology ID (GOID).
If nothing is passed in, the module
will use the top goid of each ontology
branch (i.e, goid for
molecular_function, biological_process,
or cellular_component)

-ontologyProvider Yes An ontology provider instance.

-annotationProvider No An annotation provider instance. It is
required for creating tree for GO Term
Finder result.

-termFinder No An array of hash references returned
from findTerms method of
GO::TermFinder module. It is required
for creating tree for GO Term Finder
result.

-aspect No . The aspect of the ontology
provider. It is required for creating
tree for GO Term Finder result.

-configFile Yes The configuration file for setting the
general variables for the graphic
display.

-imageDir Yes The directory for storing the newly
created image file. It must be
world (nobody) readable and writable
if you want to display the image to
the web.

-imageUrlRoot No The url root for the -imageDir. It is
required if you want to display the
image to the web.

-imageName No The image file name. By default, the
name will be something like
GOview.xxxx.png. The xxxx will be
the process id. A suffix for the image (.png
or .gif) should not be provided, as that will
be determined at run time, depending on the
capabilities of the GD library.

-treeType No . The tree type.

1. up => display the ancestor tree
for the given goid.
2. down => display the descendant tree
for the given goid.
By default, it will display the
descendant tree.

-geneUrl No The URL for each Gene to link to.
It needs to have the text in
the url which will be substituted
by the real goid for a node.

-nodeUrl No The url for each GO node to link to.
It needs to have the text in
the url which will be substituted
by the real goid for a node.

-pvalueCutOff No The p-value cutoff for displaying
the graphic for GO Term Finder.
The default is 0.01

-imageLabel No The image label which will appear at
the left bottom corner of the map.
------------------------------------------------------------------------

To display the image on the web:

$goView->showGraph;

To create and return image file name with full path:

my $imageFile = $goView->createImage;

formHandler provides a modular PHP mailscript with a lot of default modules.
formHandler is a package of PHP-scripts for basic sending of data to a mailaddress submitted in an HTML form.
This package is fully object-oriented and extremely modular. Performance is very good, and it is very easy to add home-made modules.
Several modules are included with formHandler, such as Required-module, Template-modules, Reply-module, Attachment-module, Fieldcheck-module, and Referer-module.
It is possible to use this script for every form on your site.
Whats New in 2.1.0 Development Release:
- This is a development release.
- Some small bugs have been fixed.
- Also some small features have been added. Most aliases to existing options.
- Lots of usefull documentation has been added. This documentation can also be found on the homepage. Especially usefull is the module usage documentation.
- Some options are marked to change in the future.
- A tool to check if the used version is the latest, was added.
Enhancements:
- Setcookie module created.
- Referer-check module was created.
- Log-message was created.
- Problem with double Debug-output was fixed.
- Centralization of all config-options into the configfile.inc.php file.

NOTE provides a console note management tool.
NOTE is a small console program that allows you to manage notes similar to programs like "knotes" from the command line. It supports different database backends for storage, and includes a DBI-based MySQL module and another module that uses a binary file for storage and a DBM module.
Main features:
- Several different database backends, mysql(DBI), dbm, binary(bin file), general and text (text files).
- Commandline interface using the standard perl module etopt::Long, which allows you tuse short or long command-line options.
- Interactive interface(pure ascii), the following functions are available in interactive mode: list, display, topic, delete, edit, help.
- Highly confiurable using a perlish configfile ~/.noterc. although it is configurable it is not required, note can run without a configfile using useful default presets.
- Colourized output is supported using ASCII Escape-Sequences.
- The user can customize the color for each item.
- Data can be stored in various different database backends, since all database access is excluded from the program itself in perl modules.
- Notes can be deleted, edited and you can search trough your notes.
- Notes can be categorized. Each category(topic) can contain multiple notes and even more sup-topics. There is nlimitation about sub topics.
- You can view all notes in a list and it is possible only tview notes under a certain topic.
- There is a tree-view, which allows you tget an overview of your topic-hierarchy.
- Notes can be encrypted using DES or IDEA algorythms and Crypt::CBC.
- You can dump the contents of your note database inta plain text file, which can later be imported. Imports can be appended or it can overwrite an existing database (-o).
- Note has scripting capabilities, you can create a new note by piping another commands output tnote, you can alsimport a notedump from stdin as well es duming tstdout instead a file. Additional, there is an option --raw available, which prints everything out completely without formatting.
- for better performance, note can cache the database for listings or searching.
- It can be installed without root-privileges.
- if Term::ReadLine (and Term::ReadLine::Gnu) is installed, history and auto-completion are supported in interactive mode.
- Last, a while aga user stated: "... it simply does, what it says ..."

Cow is something like a waveform editor in that it generates a wave file from one or more graphs for amplitude and frequency. It has a graphical user interface that simplifies this process.

First i wrote some classes to generate wavefiles with graphs for amplitude and frequency. Thats really simple sound synthesis. The waveformeditor of Christopher Rowley[1] inspired me. As it worked i made a little GUI just because its more compfortable to edit the
graphs... Ok. I could produce sounds, thats fine. Someone lend me a midi-keyboard and i programmed something to play the sound at different tonepitches. Well, thats it. Was a funny project, still works for me, but i guess it is dead. This will be the last release so
far. Hope you have fun with it .

cowman reads midi-events from /dev/midi00 and plays the apropriate note on /dev/dsp. You must start it with a cow-file as command-line-option or with a configfile. See manpage.

Isoqlog is an MTA log analysis program written in C. It designed to scan qmail, postfix, sendmail, exim logfile and produce usage statistics in HTML format. for viewing through a browser.
It produces Top domains output according to Incoming, Outgoing, total mails and bytes, it keeps your main domain mail statistics with Days Top Domain, Top Users values for per day, per month, and years.
Main features:
- Multi MTA support(qmail (multilog and syslog), postfix, sendmail, exim)
- Multi-domain support: Shows quite detailed statistics for not only your main domain, but also, any domain you want.
- Displays statistics for common mail delivery errors.
- For each domain you specify; displays Top incoming, outgoing, total and byte based statistics for users.
- Displays servers activity based on incoming, outgoing, total mails and size of incoming mail, for domain and its users.
- All days, all months, all years activities ( above ones ) are stored for future inspection.
- Multi-language Support ( Turkish, English, German,Portuguese,Spanish ,Italian,french, Swedish, Dutch, Polish, Norwegian, Russian, Czech, Romanian, Danish)
Enhancements:
- Zero size bug fixed.
- All Makefile.am files renewed
- "data" Directory created
- htmltemp & lang folders moved from isoqlog/ to data/
- isoqlog/isoqlog.conf-dist moved to data/isoqlog.conf-dist.in
- isoqlog.conf-dist file added to configure.in for updating prefix
- data/Makefile.am created
- CONFIGFILE variable defined in configure.in (see main.c:54-> readconfig(CONFIGFILE)
- config.h included in main.c
- you can change prefix as shown below (now it works, tested on slackware 10):
./configure --prefix=/usr/jail/ozkan

dbxbandmin collects traffic via ipchains/iptables/ipfwadm-rules and writes the data into an Interbase database. It uses Perls DBI-driver and can be extended with support for various database versions.
- You need a kernel with firewall-support
- you need ipfwadm or ipchains or iptables
- you need the InterBase-Client
- you need Perl 5.xx, pE. 5.5
- you need IBPerl0.8x
- you need DBI-Modul for Perl
- you need DBD::InterBase
(try "perl -Mcpan -e shell;" and type "install DBD::Interbase")
If you do not know what parts you needed, try install.sh for reports
First you must install a "Listening" firewall-policy. The tool tng-acc-bandminstart will do this. Follow the instructions of TNG-installation. The options-overview can you get by typing
"./tng-acc-bandmin --help", if you want a german-explanation, try "./tng-acc-bandmin --language=german --help". To remove firewall-policy use tng-acc-bandminstop.
If you have questions after reading all damn documentation, please dont hesitate to ask me for tng-acc-bandmin or marco for TNG in general.
Enhancements:
- tng-acc-bandmin.rc, tng-acc-bandmin: - added POD-documentation about all - checking if "kennung" exists - tng-acc-bandmin supports now a quiet simple and human-readable configfile - fixed misspelled words - moved short switch for "ReadDevices" from "-c" to "-r" - added switch to use a special config file (default one in current dir is "./.tng-acc-bandmin.rc"), please check documentation for side-effects - virtualization of "DBI"-driver, that means the DBI-Call is complete configurable by configfile or -switches - added an example for a configfile