Free append to software for linux

SimpleCDB - A Perl-only Constant Database.

SYNOPSIS

use SimpleCDB;

# writer
# - tie blocks until DB is available (exclusive), or timeout
tie %h, SimpleCDB, db, O_WRONLY
or die "tie failed: $SimpleCDB::ERRORn";
$h{$k} = $v;
die "store: $SimpleCDB::ERROR" if $SimpleCDB::ERROR;
untie %h; # release DB (exclusive) lock

# reader
# - tie blocks until DB is available (shared), or timeout
tie %h, SimpleCDB, db, O_RDONLY
or die "tie failed: $SimpleCDB::ERRORn";
$v = $h{$i};
die "fetch: $SimpleCDB::ERROR" if $SimpleCDB::ERROR;
untie %h; # release DB (shared) lock

This is a simple perl-only DB intended for constant DB applications. A constant DB is one which, once created, is only ever read from (though this implementation allows appending of new data). That is, this is an "append-only DB" - records may only be added and/or extracted.

Course-grained locking provided to allow multiple users, as per flock semantics (i.e. write access requires an exclusive lock, read access needs a shared lock (see notes below re. perl < 5.004)). As (exclusive) updates may be take some time to complete, shared lock attempts will timeout after a defined waiting period (returning $! == EWOULDBLOCK). Concurrent update attempts will behave similarly, but with a longer timeout.

The DB files are simple flat files, with one record per line. Records (both keys and values) may be arbitrary (binary) data. Records are extracted from these files via a plain linear search. Unsurprisingly, this search is a relatively inefficient operation. To improve extraction speed, records are randomly distributed across N files, with the average search space is reduced by 1/N compared to a single file. (See below for some example performance times.) One advantage of this flat file based solution is that the DB is human readable (assuming the data is), and with some care can be edited with a plain ol text editor.

Finally, note that this DB does not support duplicate entries. In practice, the first record found matching a given key is returned, any duplicates will be ignored.

AFD comes from Automatic File Distributor and provides a framework for very flexible, non-stop, log and debug-able delivery of an arbitrary amount of files to multiple recipients as expressed in URLs (currently mailing and ftp supported with the mailto://user@domain and ftp://user:password@host URL conventions). AFD stands for Automatic File Distributor.
The most common technique used to distribute data is for each individual to fetch the data from one common place. This place can be a database, FTP-server or even the WWW (World Wide Web). However, this is not always the most user or customer friendly way for a company or organization to distribute its products. For this reason AFD (Automatic File Distributor) was developed, to provide a better service to users or customers in transporting the required data directly to the location where it is required.
When distributing files to a remote host it does so via the FTP or SMTP protocol. Local distribution is done by simply copying files from one directory to another. To distribute files, the AFD has one central configuration file (DIR_CONFIG), where the system administrator can specify which files are to be distributed and where they are to be sent.
Main features:
- The AFD can send/retrieve any type of file, regardless of contents and the name of the file.
- Only the files are being distributed, no other additional information is send with the file.
- The AFD has a very sophisticated and compact X11 interface to monitor and control the distribution of files (afd_ctrl). It has the ability to do extensive logging of all activities, even down to tracing each individual FTP/SMTP command.
- Files can be send to places where no AFD is installed.
- There can be more than one process distributing files to a single host. This has the advantage that when a large file is currently being distributed, other files dont have to wait until the large file is done.
- Where net capacity is limited, it is possible to distribute files with priority.
- If the transfer gets interrupted, AFD can append files. So data that has already been transmitted will not be send again.
- It is possible to setup a whole network of AFDs that can be monitored and controlled through a single interface (mon_ctrl).
Version restrictions:
- The AFD requires X11R5 and Motif 1.2.x (or higher).
Enhancements:
- Files that have been distributed or are to be distributed can now be viewed via show_olog and show_queue dialog.
- A new interface for acknowledging errors was added.
- All events are logged into a separate log file.
- The pattern matching function was enhanced so that it can also handle [] brackets.
- More syntax checks were added for options in DIR_CONFIG.

ABacoD is an automatic backup script.

Transfers files and directory renaming them with a configurable logic.

Source path can contain wildchars:

* :every string
? :every char
[...] :one specified char

Destination path can contain:

^n^ :replaced with the result of n-th expansion in source path (starting from 0)
^d^ :replaced with hour/date of the trensfer (the format is configurable)

Accept command line argumnt and/or a configuration file. Command line argument overwrite corresponding configuration files. Append implies deletion of source file.
Does not implements loops, therefore you must use cron or similar systems.

IMPORTANT NOTE: - Abacod deletes files! Testing parameters with the DUMMY (or -t) flag is safety. More safety is run with a user whose rights are the minumum possible.

Syntax

abacod [OPTION] CONFIGFILE"

-V, --version print version
-h, --help print this help
-v, --verbose print what is going to do
-t, --test dont touch filesistem, print only
-p, --srcpath SRCPATH source path (can use wildchar: *,?,[...])
-d, --dstpath DSTPATH destination path:
^n^ is replaced with n-th wildchar
^d^ is replaced with current date
-r, --deletesrc delete source
-i, --ignoredirs ignore subdirs of srcpath
-a, --append append
-o, --overwritemode MODE overwrite mode:
0: never
1: ever
2: only if newer
3: only if bigger
-m, --maxtransfer AMOUNT stop after AMOUNT transfer
-s, --transfersleep SEC sleep between transfer (default 1)
--errorsleep SEC sleep before exit on error (default 30)
-u, --forcedumask UMASK umask to use
--forcedowner ID set owner ID
--forcedgroup ID set group ID
-e, --dateformat FORMAT format to use for date (date syntax)
--testmountpoint MOUNTPOINT test mountpoint before proceeding
--testping ADDRESSORNAME ping this address before proceeding

every command line values overwrites configuration file one if there is no configuration file command ends with a -

Tree::Numbered is a thin N-ary tree structure with a unique number for each item.

SYNOPSYS

use Tree::Numbered;
my $tree = Tree::Numbered->new(John Doe);
$tree->append(John Doe Jr.);
$tree->append(Marry-Jane Doe);

while (my $branch = $tree->nextNode) {
$branch->delete if ($branch->getValue eq Stuff I dont want);
}

my $itemId = what_the_DB_says;
print join --- , $tree->follow($itemId); # a list of items up to itemId.

$tree->allProcess( sub {
my $self = shift;
$self->getValue =~ /^(S*)/;
$self->addField(FirstName, $1);
} );

etc.

Tree::Numbered is a special N-ary tree with a number for each node. This is useful on many occasions. The first use I found for that (and wrote this for) was to store information about the selected item as a number instead of storing the whole value which is space-expensive.

Every tree also has a lucky number of his own that distinguishes it from other trees created by the same module. This module is thin on purpose and is meant to be a base class for stuff that can make use of this behaveiour. For example, I wrote Tree::Numbered::DB which ties a tree to a table in a database, and Javascript::Menu which uses this tree to build menus for websites.

One more feature that the module implements for the ease of subclassing it is an API for adding and removing fields from trees and nodes.

IPChains is a Perl module to create and manipulate ipchains via Perl.

SYNOPSIS

use IPChains;
$fw = IPChains->new(-option => value, ... ); $fw->append(chain);

This module acts as an interface to the ipchains(8) userspace utility by Paul "Rusty" Russell (http://www.rustcorp.com/linux/ipchains/). It attempts to include all the functionality of the original code with a simplified user interface via Perl. In addition, plans for log parsing facilities, an integrated interface to ipmasqadm, and possibly traffic shaping are slated for up and coming versions.
The new() and attribute() methods support the following options:

Source

Specifies origination address of packet. Appending hostmask to this address using a / is OK, as well as specifying it separately (see SourceMask).

SourceMask

Hostmask for origination address. Can either be in 24 or 255.255.255.0 style.

SourcePort

Specific port or port range (use xxx:xxx to denote range), requires specific protocol specification.

Dest

Specifies destination address of packet. Appending hostmask to this address using a / is OK, as well as specifying it separately (see DestMask)

DestMask

Destination address, (see SourceMask).

DestPort

Destination Port, (see SourcePort).

Prot

Protocol. Can be tcp, udp, icmp, or all. Required for specifying specific port(s).

ICMP

ICMP Name/Code (in place of port when ICMP is specified as protocol).

Here is a small table of some of the most common ICMP packets:

Number Name Required by

0 echo-reply ping
3 destination-unreachable Any TCP/UDP traffic.
5 redirect routing if not running
routing daemon
8 echo-request ping
11 time-exceeded traceroute

Rule

Target. Can be ACCEPT, DENY, REJECT, MASQ, REDIRECT, RETURN, or a user-defined chain. Note: This is case sensitive.

Interface

Specify a specify interface as part of the criteria (ie, eth0, ppp0, etc.).

Fragment

Rule only refers to second and further fragments of fragmented packets (1 or 0).

Bidir

Makes criteria effective in both directions (1 or 0).

Verbose

Set verbose option for setting rules or list() (1 or 0).

Numeric

Show output from list() in numeric format. No DNS lookups, etc.. (1 or 0).

Log

Enable kernel logging (via syslog, kern.info) of matched packets (1 or 0).

Output

Copy matching packets to the userspace device (advanced).

Mark

Mark matching packets with specified number (advanced).

TOS

Used for modifying the TOS field in the IP header. Takes 2 args, AND and XOR masks, (ie, (TOS => ["0x01", "0x10"])). This feature is highly untested.
The first mask is ANDed with the packets current TOS, and the second mask is XORed with it. Use the following table for reference:

TOS Name Value Typical Uses

Minimum Delay 0x01 0x10 ftp, telnet
Maximum Throughput 0x01 0x08 ftp-data
Maximum Reliability 0x01 0x04 snmp
Minimum Cost 0x01 0x02 nntp

Exact

Display exact numbers in byte counters instead of numbers rounded in Ks, Ms, or Gs (1 or 0).

SYN

Only match TCP packets with the SYN bit set and the ACK and FIN bits cleared (1 or 0).

DenyHosts is a script intended to be run by Linux system administrators to help thwart ssh server attacks.
If youve ever looked at your ssh log (/var/log/secure on Redhat, /var/log/auth.log on Mandrake, etc...) you may be alarmed to see how many hackers attempted to gain access to your server. Hopefully, none of them were successful (but then again, how would you know?). Wouldnt it be better to automatically prevent that attacker from continuing to gain entry into your system?
DenyHosts attempts to address the above... and more.
Main features:
- Parses /var/log/secure to find all login attempts and filters failed and successful attempts.
- Can be run from the command line, cron or as a daemon (new in 0.9)
- Records all failed login attempts for the user and offending host
- For each host that exceeds a threshold count, records the evil host
- Keeps track of each non-existent user (eg. sdadasd) when a login attempt failed.
- Keeps track of each existing user (eg. root) when a login attempt failed.
- Keeps track of each offending host (with 0.8+ these hosts can be purged if the associated entry in /etc/hosts.deny is expired)
- Keeps track of suspicious logins (that is, logins that were successful for a host that had many login failures)
- Keeps track of the file offset, so that you can reparse the same file (/var/log/secure) continuously (until it is rotated).
- When the log file is rotated, the script will detect it and parse from the beginning.
- Appends /etc/hosts.deny and adds the newly banned hosts
- Optionally sends an email of newly banned hosts and suspicious logins.
- Keeps a history of all user, host, user/host combo and suspicious logins encountered which includes the data and number of corresponding failed login attempts.
- Maintains failed valid and invalid user login attempts in separate files, such that it is easy to see which valid user is under attack (which would give you the opportunity to remove the account, change the password or change its default shell to something like /sbin/nologin
- Upon each run, the script will load the previously saved data and re-use it to append new failures.
- Resolves IP addresses to hostnames, if available (new in v0.6.0).
- /etc/hosts.deny entries can be expired (purge) at a user specified time (new in 0.8)
- FreeBSD support (added in 0.7)

Yet Another dia2sql is a tool that generates SQL statements from Dia XML files.

yadia2sql is intended to process diagrams that are compatible with dia2sql.php to some point, and provide features that would allow generation of SQL code for different database systems from single Dia source.

Usage:

yadia2sql.py [OPTIONS...]

Options:

-h | --help | -?
Prints short usage and copyright information.
-i filename | --input filename
Specify input file (must be an uncompressed Dia XML file).
-o filename | --output filename
Specify output file.
-p "text" | --pk-append "text"
Append text text to primary key definitions.
-f "text" | --fk-append "text"
Append text text to foreign key definitions.
-t "text" | --tbl-append "text"
Append text text to table definitions.
-m filename | --map-file filename
Specify substitution map file.
-d database | --database database
Specify database system (currently only mysql is supported).
If no input/output file is specified, stdin/stdout is used.