Free stores software for linux

Confstore is a configuration backup utility. Confstore scans your system for all recognised configuration files and then stores them in a archive. Confstore can also restore configuration from a previously created archive.

StoreBackup is a backup utility that stores files on other disks.

It includes several optimizations that reduce the disk space needed and improve performance, and unifies the advantages of traditional full and incremental backups.

Depending on its contents, every file is stored only once on disk. It includes tools for analyzing backup data and restoring. Once archived, files are accessible by mounting filesystems (locally, or via Samba or NFS). It is easy to install and configure.

D_store is an in memory database. A good mental model for d_store is a programmatic spreadsheet; there are rows and rows contain fields with values.

D_store is mostly row oriented, all stores represent either all the rows in the spreadsheet or a subset thereof (or the empty set). The query powers of d_store come from the set operations you can do with stores, like and, or, sub, etc.

Why D_store ?

D_store is good for storing highly related data and performing queries on that data. It can however only scale to the amount of memory available. But, this fits very well for GUI applications that let users interact with a lot of interrelated data; d_store is ment as an enabler of rich applications like iTunes, or addressbooks, or bookmark managers etc.

D_store supports tagging, full text searching, hierarchies, and almost any relation you can define on your data. The API provides very direct access to the data, unlike, for instance SQL engines, but it still has the query power as SQL.

In d_store, all data is stored as values, but every value is stored only once per store, which is good for memory usage. And this is where the second part of the querying power of d_store comes from: every value knows in which rows it appears.

A last powerful concept that d_store has is that everything operates on stores, and the results sets are always stores. So when you get the results of a query, you can query that result again and again, refining the results further and further.

The project is written in plain C and released under the GPL.

Email::Store::DBI is a Perl module for database backend to Email::Store.

SYNOPSIS

use Email::Store dbi:...;

This class is a subclass of Class::DBI and contains means for Email::Store-based programs to register what DSN they wish to use. It also provides for building database tables from schemas embedded in the DATA section of plug-in modules, using Class::DBI::DATA::Schema.

"Email::Store" is the ideal basis for any application which needs to deal with databases of email: archiving, searching, or even storing mail for implementing IMAP or POP3 servers.

"Email::Store" itself is a very lightweight framework, meaning it does not provide very much functionality itself; in effect, it is merely a Class::DBI interface to a database schema which is designed for storing email. Incidentally, if you dont know much about "Class::DBI", youre going to need to in order to get much out of this.

Despite its minimalist nature, "Email::Store" is incredibly powerful. Its power comes from its extensibility, through plugin modules and hooks which allow you to add new database tables and concepts to the system, and so access the mail store from a "different direction". In a sense, "Email::Store" is a blank canvas, onto which you can pick and choose (or even write!) the plugins which you want for your application.

For instance, the core "Email::Store::Entity" plugin module addresses the idea of "people" in the email universe, allowing you to search for mails to or from particular people; (despite their changing names or email addresses) "Email::Store::Thread" interfaces "Email::Store" to "Mail::Thread" allowing you to navigate mails by their position in a mail thread; the planned non-core "Email::Store::Plucene" module plugs into the indexing process and stores information about emails in a Plucene search index for quick retrieval later, and so on.

steelpoll is a Web polling application which allows you to quickly and easily create and manage polls by just editing plain Tcl files. A single poll can be created by editing the variables in a single file.

You can optionally control votes by checking the users IP address. A parsed vote log can be viewed. It doesnt require any SQL database backend because it stores the results in easily parsed plain text files. The project doesnt use graphics to display poll results, which is great for text-based Web browsers.

listener is a typical security-related program like the motion package (which detects motion on a Webcam): it listens for sound.

If listener detects any sounds, it starts recording until the sound stops (or a bit later, which is configurable). It stores the audio in .WAV files.

I would like to add a low-, high- and bandfilter to listener (plugins). Ive googled but could not find a simple example on how to implement this. So if anyone can help me?

Starfish Password Manager project consists of a password manager.
Starfish is a simple password manager. It stores all of its data in XML, and uses strong encryption (MD5 with DES).
Main features:
- 100% Java©
- Easy to use GUI
- Strong encryption
- Sortable columns, password hiding/unhiding
- Easy copy to clipboard
- All data stored in XML

PurePostPro provides an upload post-processor for Pure-FTPd.

PurePostPro is a Perl/MySQL script that enables user uploads to be managed more easily. New uploads are logged in a MySQL database, and duplicate files are tracked using MD5 checksums.

The script has two main functions:

1. It logs all incoming uploads to a two-table database;

2. It calculates an MD5 checksum for each file and stores that in the database too.