Free db solo 2.2.4 software for linux

LeoArg can parse easily commandline options. The class only uses standard libraries.
Installation:
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean. There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Enhancements:
- COPYING: Licence changed from GPL to BSD

ArX is a Revision Control System (RCS), like CVS, Subversion, or GNU arch. It manages "archives" (collections of files), such as source code files for a software project.
ArX tracks the history of each file, along with change comments, version tags, forks and branches, etc. It can store files and documents of any kind, but the largest benefits are with text files, rather than binary files.
Main features:
- Ease of learning and use
- Powerful branching and merging features
- Speed, even when working with large repositories
- Effective distributed development
- Friendly and helpful user and developer communities
- Cryptographic data integrity features
- Ability to publish archives on almost any server
- Portability to multiple operating systems (still in progress)
Like CVS (and most modern RCS tools), ArX uses an "optimistic" locking model, which allows multiple developers to modify the same file at the same time, and then resolves any conflicts as each developer checks in his or her work. While this may sound scary if you are used to systems that "lock" files, it actually works very well, as confirmed by the thousands of projects that have used this approach (in CVS) for many years.
Unlike CVS and most traditional RCS tools, ArX is "distributed", which means that ArX does not require a central server. Each developer can maintain their own "archive" of their projects, but can easily share their work with other developers. This modern design works well with teams that are geographically distributed, and especially with teams where some contributors are not part of the core team.
ArX includes an optional patch queue manager to enable centralized, CVS-style, development when desired. ArX differs from many of the newer distributed SCM tools in that it does not require every working tree to contain an entire copy of the archive history.
Each archive can store multiple branches, each of which could be checked out in multiple working trees. Other tools may use the terms "patch pooling" or "centralized storage" for this type of feature, and it is important for efficient branching on systems without hardlinks. Also, ArX archives can link to other archives (including remote archives) for older history, allowing branches of remote projects to be very small and fast.
Another important feature of ArX is that an archive can be published on any HTTP web server. It does not require any special code running on the server, which has some significant advantages: First, it allows projects to host their code on almost any inexpensive web site, including the free personal home pages offered by many ISPs. Second, it keeps the server very secure, because the only service required is a standard web server such as Apache or Boa.
Enhancements:
- ArX now uses three-way merging as a default, and supports third party merge tools.
- ArX is also much more clever about renames.
- "merge" now uses the --update option instead of using heuristics.
- ArX now records when there are conflicts in the tree, and will not let you commit unless they are resolved.
- ArX now uses -v and -q for verbosity.
- "commit" now supports --author and --date options for Tailor.
- The patch queue manager has been updated, and some small bugs were fixed.

VTSurvey is a browser-based tool which enables end users to autonomously create and run online surveys, feedback or registration forms.
By providing a forms-based visual editor, the use of VTSurvey requires no programming knowledge or skills in HTML.
VTSurveys built-in user management system enables it to serve large organizations and facilitates collaborative survey development and administration
Main features:
- Forms-based visual editor for survey creation
- User authentication via internal user database (XML-based) and/or external via LDAP
- Customizable layout (header, footer, colors, styles)
- Enables use of HTML for special-purpose customization (optionally)
- Restrict allowed respondends by user-IDs or shared password (optionally)
- Restrict to only one response per user (optionally)
- E-mail notification for incoming results
- View results online
- Password-protect viewing of results (optionally)
- Export of results to Microsoft Excel, SAS, SPSS or similar (via CSV formats)
- Support for collaborative development (multiple survey admins)
- Internationalization support and translations into many languages

BW Acct is a bandwidth accounting and reporting application. It is implemented as a C daemon which manages accounting rules in an iptables/netfilter firewall on the Linux 2.4 kernel.
Support for multiple RDBMS is included, and a plugin architecture is provided for extending BW Acct to support other databases. BW Acct can provide accurate accounting of just about any firewall rule.
BW Acct runs in the background and monitors a database for updates. Based on these updates it manages the firewall rules. Rules are inserted before any other rules in the standard netfilter chains. This allows accounting data to be processed before any other rules take effect. For example, this allows you to account all ICMP traffic received by the system, even if a later rule drops some of this traffic.
Extract the bwacct tarball
read the README in the source directory
make
After building bwacct, youll want to build either the sqlite or mysql database plugin. Either make sqlite or make mysql
Quick setup. (for sqlite)
mkdir /bwacct
mkdir /bwacct/db
chmod 770 /bwacct/db
chgrp nobody /bwacct/db
cp accounting.db /bwacct/db
chmod 660 /bwacct/db/accounting.db
chgrp nobody /bwacct/db/accounting.db
cp bwacct match_*.so target_*.so bwacct.conf sql_*.so /bwacct
chmod 755 /bwacct/bwacct
Edit /bwacct/bwacct.conf. To start you only need to modify the path for accounting.db. "db/accounting.db"
cd /bwacct
./bwacct -f bwacct.conf
Enhancements:
- A signed 16-bit integer overflow on table id has been fixed.

check_logfiles is a plugin for Nagios which checks logfiles for defined patterns. check_logfiles project is capable of detecting logfile rotation.

If you tell it how the rotated archives look, it will also examine these files. Unlike check_logfiles, traditional logfile plugins were not aware of the gap which could occur, so under some circumstances they ignored what had happened between their checks.

A configuration file is used to specify where to search, what to search, and what to do if a matching line is found.

Installation:

1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.

Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.

2. Type `make to compile the package.

3. Optionally, type `make check to run any self-tests that come with the package.

4. Type `make install to install the programs and any data files and documentation.

5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean. There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.

p0f-db project is a modified version of p0f that puts its data into a database.
Usage:
All the standard p0f options applies. To get p0f to log data into DB you need:
- Get modified p0f files (see links at the end of this page).
- Extract them from the tarball.
- Compile and install p0f with modified "mk/Linux" (this is a Makefile) according to your DB type, include paths, library paths and any other compiler options.
- Create DB and tables for p0f (see "create_..." files in downloaded tarball).
- Modify your "/etc/p0f/p0f-db.conf" to reflect your DB setup.
- Run p0f and see tables populating.

pysqlite is a Python DB-API 2.0 interface for the SQLite embedded relational database engine.
Enhancements:
- pysqlite is now 2.5 times faster for DML statements.
- This pays off especially for bulk-loading data.
- pysqlite now recognizes if the database engine has done an implicit ROLLBACK and acts accordingly.
- Using custom mapping and sequence types in parameters works now.

Db::DFC is the Perls Object-oriented interface to Documentums DFC.

SYNOPSIS

use Db::DFC;
$dfc = Db::DFC->new();

$DOCBASE = "docbase";
$USER = "user";
$PASSWORD = "passwd";
$DOMAIN = "domain";
$FILE = $0;

$dfclient = DfClient->new();
$idfclient = $dfclient->getLocalClient();
$idflogininfo = DfLoginInfo->new();

$idflogininfo->setUser($USER);
$idflogininfo->setPassword($PASSWORD);
$idflogininfo->setDomain($DOMAIN);

$idfsession = $idfclient->newSession($DOCBASE,$idflogininfo);

$pobj = $idfsession->newObject("dm_document");
$doc = $dfc->castToIDfDocument($pobj);

$doc->setObjectName("this file");
$doc->setContentType("crtext");
$doc->setFile($FILE);
$doc->save();

print "nDocument Id:" . $doc->getObjectId()->toString() . " created.n";
$idfsession->disconnect;