Free static software for linux

Cache::Static is a Perl module used for caching without freshness concerns.

SYNOPSIS

HTML::Mason instructions

In handler.pl: use Cache::Static;

In any component you where you have a well defined set of dependencies which change the output:

< %init >
my $_cs_deps = [
#file dependencies - only regenerate if a file has changed
file|/path/to/some_configuration_file,

#DBI dependencies - still under development - WONT WORK
#DBI dependencies: note the third argument is a DSN
_DBI|table|mysql:scache_test_db|test_table,
_DBI|db|mysql:scache_test_db,

#not yet implemented:
#column level depends, e.g. "DBI|column|$dsn|$tablename|$columname"
#row depends, e.g. "DBI|row|$dsn|$tablename|$uid_column_name|$uid_value"

#XML::Comma dependencies - only regenerate if a Doc or Store has changed
"_XML::Comma|Doc|$doc_key",
"_XML::Comma|Store|$def|$store",

#time dependencies (WARNING: these are discouraged, see doc/NOTE-time-deps)
time|15s, #every 15 seconds
time|M:15s, #every 15 seconds after the minute
time|H:2m, #every 2 minutes past the hour
time|W:2d3h5m0s, #every Tuesday at 3:05 AM

#modifiers (indicate behavior when the file cannot be found)
file-0|/tmp/foo, #if ! -e /tmp/foo, regenerate
file-1|/tmp/foo, #if ! -e /tmp/foo, serve
file|/tmp/foo, #use config value "dep_file_not_found_returns"

#note modifiers also work on extensions, e.g.
_DBI-1|db|mysql:scache_test_db,
_XML::Comma-0|Store|mm_item|post,

#etc... but modifiers CANNOT be used with times (since they have no
#file backing on disk)
];

#whatever you have in $_cs_deps above...
return if Cache::Static::HTML_Mason_Util::cache_it($r, $m, 1, $_cs_deps);

#...
#rest of init block
#...
< /%init >

dim_STAT project is a performance analysis and monitoring tool for Solaris and Linux (as well all other UNIX) systems.
Main features:
- Web based interface
- data storage in a SQL database
- several data views
- interactive (Java) or static (PNG) graphs
- real-time monitoring
- multi-host monitoring
- post analyzing
- statistics integration
- professional reporting with automated features, and more.

smalloc short from Static memory buffer malloc, is an ideal memory manager for Realtime Linux Kernel modules that cant use dynamic memory offered by kmalloc because of the non-realtime nature of kmalloc.

Like malloc(), smalloc() doles out memory to client code. Unlike malloc, however, smalloc takes a static memory buffer (as an initialization parameter). It is this buffer that smalloc manages when doling out memory to client code.

This design makes smalloc ideal for use inside a Realtime Linux kernel module. It also makes it much easire to port userspace code that relies on malloc() in C or operator new() in C++ for memory management to a realtime kernel module.

For example:

(the below is linux kernel code)

< code >

#include "smalloc.h"
#include < linux/slab.h >

#define MEMPOOLSZ (1024*1024*1024)
char *buf;

...

buf = kmalloc(MEMPOOLSZ, GFP_KERNEL); /* 1 megabyte buffer in kernel
module.. */
smalloc_set_memory_pool(buf, sizeof(buf));

...

MyStruct *s;

s = smalloc(sizeof(MyStruct)); /* example of code that uses this
static memory buffer */

< /code >

The above example is a typical usage pattern of smalloc.

aircrack is a 802.11 sniffer and WEP/WPA key cracker.
It consists of: airodump (an 802.11 packet capture program), aireplay (an 802.11 packet injection program), aircrack (static WEP and WPA-PSK cracking), and airdecap (decrypts WEP/WPA capture files).
Enhancements:
- airodump: show probing clients as "not associated"
- airodump: dont substract the noise level unless madwifi
- airodump: fixed channel hopping with old orinoco
- airmon.sh: added detection of the zd1211 driver

Standalonecomplex is a banner scanner used for profiling subnets. Standalonecomplex project has built in nmap support as well as static port profiling.

Usage:

./standalonecomplex [-h] [-c < file >] [-r < range >] [-l < log >]

-h : print this screen.
-v : display only vulnerable hosts.
-c < file > : configuration file.
-l < log > : file to log output to (default is stdout).
-r < range > : ip range to scan.

mysqlApache is a MySQL database backend and browser based frontend for managing large numbers of Apache web servers (each of more than a 1000 virtual and IP-based web sites).

It is part of the OpenISP project and works if you like with mysqlBind, mysqlISP, mysqlIPM, and mysqlSendmail.

Our mysqlISP component systems focus is on a very stable telco quality ISP services via static configuration of servers from mySQL, but with mySQL not required to be live.

Synergiser is a Content Management System (CMS) that does not rely on a database.

It features a simple blog system, TinyMCE editors for all relevant sections, a module architecture, simple menu and poll modules, a settings manager for module settings and template/locale, a Page File Manager for managing static pages, and a template system with definable regions.

FlightFeathers goal is "social networking for everyone". This means that anyone should have a chance to run a popular social networking site -- on minimal hardware, and without wasting bandwidth.
FlightFeathers design has reflected its goal from the very beginning. Whenever the systems state changes, FlightFeather generates static HTML pages. Pure read operations -- usually about 90% of the total -- do not require the application to run at all.
FlightFeathers sister project -- Flightdeck-UI -- likewise uses this Relative Static technique (i.e. the application-generated dynamic data appears as static pages to the Web server). The author also presented these concepts at LinuxWorld San Francisco 2006.
FlightFeather does not use a separate SQL database. In-memory data structures and Berkeley DB augment the static HTML pages to maintain a consistent state. The overall approach may be termed LAP -- a variation on the highly effective LAMP platform. LAMP stands for Linux, Apache, MySQL and Perl/Python/PHP (although there can be further variations).
FlightFeather drops the "M" from this formula, in favor of capturing as many system state changes as possible into complete, static HTML documents. Apache can then serve these documents by itself, while FlightFeather waits in the background.
Enhancements:
- This release modifies the way the FlightFeather server loads the configuration, protocol, session, and storage modules on startup.
- The actual loading process now takes place after all options have been parsed.
- If the "-c" or "--command" option is present, the server does not import these modules at all, since they are not required.
- The new implementation also fixes a bug that caused the test versions of the above modules to always load, in addition to any modules specified on the command line.