Free to record software for linux

QARecord is a simple multithreaded stereo recording tool. QARecord project can record both 16 bit and 32 bit WAVs.

By using a large ringbuffer for the captured data, buffer overruns are avoided. QARecord can also be used as JACK client.

RecordRadio is a basic bash script that plugs into amarok and uses streamripper to record radio stations you listen to and add the songs into your music collection.

RecordRadio script is not very sophisticated right now but it should be easy for anyone to edit or enhance.

Simply enable it as a plugin, and when you connect to any URL that starts with http:// the plugin will spawn a instance of streamripper that will record the songs and place them in subdirectories within a directory called "Music" in your home.

Five seconds after connecting to the recording has started amarok will start listening to streamrippers relay server on port 8017 so as not to use twice as much bandwidth as needed.

Because of its simplistic design it has the following shortcomings:

If you wish to change the streamripper options or the directory where things get stored you have to edit the file manually.
(This can be fixed as soon as a dcop interface is provided to preferences.)
When you start an internet radio station your playlist will be cleared.
(This can be fixed as soon as the amarok developers fix the playMedia dcop call)
There is a five second delay before everything is running.
Sometimes the server is full and cannot support an additional connection for streamripper so you cant record that station.

RecordRadio is released under the GPL.

Geo::TigerLine::Record::B is a TIGER/Line 2003 Polygon Geographic Entity Codes: Corrections.

SYNOPSIS

use Geo::TigerLine::Record::B;

@records = Geo::TigerLine::Record::B->parse_file($fh);
@records = Geo::TigerLine::Record::B->parse_file($fh, &callback);

$record = Geo::TigerLine::Record::B->new(%fields);

$record->rt();
$record->version();
$record->file();
$record->cenid();
$record->polyid();
$record->statecq();
$record->countycq();
$record->tractcq();
$record->blockcq();
$record->aianhhfpcq();
$record->aianhhcq();
$record->aihhtlicq();
$record->aitscecq();
$record->aitscq();
$record->anrccq();
$record->concitcq();
$record->cousubcq();
$record->submcdcq();
$record->placecq();
$record->uacc();
$record->urcc();
$record->rs_b1();

This is a class representing record type B of the TIGER/Line 2003 census geographic database. Each object is one record. It also contains methods to parse TIGER/Line record type B files and turn them into objects.

This is intended as an intermediate format between pulling the raw data out of the simplistic TIGER/Line data files into something more sophisticated (a process you should only have to do once). As such, its not very fast, but its careful, easy to use and performs some verifications on the data being read.

As this class is autogenerated by mk_parsers, think before you modify this file. Its OO, so consider sub-classing instead.

MailRecon is Unix email content control application. It does listen network traffic, capture SMTP messages, analyse it (checks against very flexible and extendable checklist), discards usual private/business messages and save suspicious messages for detailed inspection by security staff.
Main features:
- Capturing email messages from the wire. So its compatible will all mailing software, do not require any reconfiguration and captures messages even if its sent directly to recipient bypassing your mailserver.
- Support for SMTP and POP3 protocols.
- Very flexible mailing filter which goes with MailRecon allows to record only suspicious messages which worth to be examined, and skip usual private and business messages.
- Open Architecture. MailRecon supports plugins for analysis and save of messages. Its very easy to extend its functionality with new plugins - every programmer and system administrator can write it.
- Thanks to Open Architecture, you can use your favorite mail reader or browser to manage archive of captured suspicious messages.
- For limited time, WWW-Security offers free installation and support of evaluation versions on your servers.
- FREE evaluation version which is never expires!
Installation:
- Create user mailrecon and groups mailrecon and mail
- From installation directory run "make install" (as root)
- Copy init.d/mailrecon to your init.d directory and optionally create symlinks from rcN directories if you want to automatially start mailrecon on boot.

EnsEMBL::Web::Record is a family of modules used for managing a users persistant data in a database.

SYNOPSIS

Many web sites now encourage users to register and login to access more advanced features, and to customise a site to their needs.

The EnsEMBL::Web::Record group of Perl modules is design to manage any arbitrary type of user created data in an SQL database. This module follows the Active Record design pattern, in that each new instantiated Record object represents a single row of a database.

That object can be manipulated programatically, and any changes made can be stored in the database with a single record->save function call.

Because arbitrary Perl data structures can be stored in this manner, EnsEMBL::Web::Record allows user preferences to be easily saved, and allows developers to implement new featurs quickly.

This module was first used (and has been abstracted from) the Ensembl genome browser (http://www.ensembl.org).

New user data can be added to the database:

use EnsEMBL::Web::Record;

my $bookmark = EnsEMBL::Web::Record->new();
$bookmark->url(http://www.ensembl.org);
$bookmark->name(Ensembl);
$bookmark->save;
...

The Record can be associated with an user id:

$record->user($id);

The same record can also be removed:

$bookmark->delete;

EnsEMBL::Web::Record also provides a number of methods for getting collections of records from the database, using a field selector.

EnsEMBL::Web::Record::find_bookmarks_by_user_id($id).

StoryTestIQ is a tool for creating "Executable Requirements" which have also been known as acceptance tests or functional tests. STIQ was developed based on two other open source acceptance testing tools, Selenium and FitNesse.

This combination allowed StoryTestIQ to capture the web browser based testing facilities and elegant command language of Selenium along with the wiki based editing and pluggable Fit fixture loading of FitNesse. We believe that this increases the productivity of working with StoryTestIQ and also enhances the capabilities of Selenium to test beyond the user interface.

When developing web applications it is helpful for the cross-functional team to have a definitive and executable view of the requirements for a specified iteration.

StoryTestIQ may be used to record what the teams customer needs and get sign off before developing even a single line of code. Most of the test cases which are recorded will be failing. It is the responsibility of the team to implement the requirements in order to make the test cases pass. These practices are based in the tradition of Test-Driven Development.

Although teams would benefit greatly from the above approach in which your entire cross-functional team including the customer, business analyst, QA, development, and anybody else providing input on the product benefits, StoryTestIQ does not enforce this approach.

StoryTestIQ may also be used in traditional development teams to create acceptance and functional tests. They may be used to supplement the teams unit tests with a Test-Driven Development approach or even to automate existing manual test cases.

Check out the page on how to get started. Once you have StoryTestIQ running successfully, take a look at the users guide for more details on how to create test suites and test cases. As you become familiar with creating test cases you may take advantage of more StoryTestIQ commands in your functioanl tests.

HTTP::Server::Simple::Recorder is Perl module for mixin to record HTTP::Server::Simples sockets.

SYNOPSIS

package MyServer;
use base qw/HTTP::Server::Simple::Recorder HTTP::Server::Simple::CGI/;

sub recorder_prefix { "path/to/logs/record" } # defaults to /tmp/http-server-simple-recorder

# logs to path/to/logs/record.34244.1.in,
# path/to/logs/record.34244.1.out,
# path/to/logs/record.34244.2.in,
# path/to/logs/record.34244.2.out, etc, if 34244 is the PID of the server

This module allows you to record all HTTP communication between an HTTP::Server::Simple-derived server and its clients. It is a mixin, so it doesnt itself subclass HTTP::Server::Simple; you need to subclass from both HTTP::Server::Simple::Recorder and an actual HTTP::Server::Simple subclass, and HTTP::Server::Simple::Recorder should be listed first.

Every time a client connects to your server, this module will open a pair of files and log the communication between the file and server to these files. Each connection gets a serial number starting at 1. The filename used is >, then a period, then the connection serial number, then a period, then either "in" or "out". recorder_prefix defaults to /tmp/http-server-simple-recorder, but you can override that in your subclass. For example, you might want to include the process ID.