Free softflowd 0.9.8 software for linux

Wflogs is a firewall log analysis tool. It can be used to produce a log summary report in plain text, HTML and XML, or to monitor firewalling logs in real-time.
This project is part of the WallFire project, but can be used independently.
Usage examples:
wflogs -i netfilter -o html netfilter.log > logs.html
converts the given netfilter log file into a HTML report.
wflogs --sort=protocol,-time -i netfilter -o text netfilter.log > logs.txt
converts the given netfilter log file into a sorted (by protocol number, then reverse time) text report.
wflogs -f $start_time >= [this 3 days ago] && $start_time < [this 2 days ago] && $chainlabel =~ /(DROP|REJECT)/ && $sipaddr == 10.0.0.0/8 && $protocol == tcp && ($dport == ssh || $dport == telnet) && ($tcpflags & SYN) -i netfilter -o text --summary=no
shows log entries (without summary) which match the given expression (refused connection attempts that occured 3 days ago to ssh and telnet ports coming from internal network 10.0.0.0/8).
wflogs -i netfilter -o text --resolve=0 --whois=0 netfilter.log
converts the given netfilter log file into a text report (default mode), disabling IP address reverse lookups and whois lookups.
wflogs -i netfilter -o xml netfilter.log > logs.xml
exports netfilter logs in XML.
wflogs -i ipchains -o netfilter ipchains.log > netfilter.log
converts ipchains logs into netfilter log format. So you may process them with your favorite netfilter log analyser, for example (even if the latter may not be better than wflogs itself.
wflogs -i ipfilter -o human --datalen=yes ipfilter.log
produces a report about ipfilter logfile in natural language on stdout, displaying packet length (datalen option) which is not showed by default.
wflogs -R -I
monitors logs in real-time in an interactive shell, waiting for logs in the default system logfile, in guessed format (according to the local firewalling tool).
Supported systems
WallFire is intended to work on real systems such as Unix, especially Linux and *BSD.
Current wflogs input modules are:
- netfilter (Linux 2.4 and 2.6 firewall logs)
- ipchains (Linux 2.2 firewall logs)
- ipfilter (NetBSD, FreeBSD, OpenBSD, Solaris, SunOS 4, IRIX and HP-UX running ipfilter firewall logs).
- cisco_pix (Cisco PIX filter logs)
- cisco_ios (Cisco IOS filter logs)
- snort (Snort ACLs logs)
Please note that input modules are available on any architecture on which wflogs can run (for example, you can perfectly parse Cisco PIX logs on a Linux box).
Enhancements:
- Improved matching of netfilter and ipfilter input modules.
- Added support for Cisco FWSM (PIX).
- Improved netfilter parsing.
- Compilation fixes for *BSD.
- Added wflogs.dtd.
- Added wfchkintegrity tool, which enables to monitor changes in the firewalling configuration.
- Fixed buffer sizes for some input modules.
- Fixed parsing with recent flex versions.

RefDB is a reference database and bibliography tool for SGML, XML, and LaTeX/BibTeX documents.
RefDB allows users to share databases over a network. RefDB is lightweight and portable to basically all platforms with a decent C compiler. And its released under the GNU General Public License.
RefDB appears to be the only available tool to create HTML, PostScript, PDF, DVI, MIF, or RTF output from DocBook or TEI sources with fully formatted citations and bibliographies according to publishers specifications (check out some examples). Additional document types can be easily added.
Main features:
- RefDB is a reference/notes database and bibliography tool for SGML, XML, and LaTeX documents.
- RefDB is mainly implemented in C, with a few Perl scripts inbetween, as well as shell scripts as "glue". It can be compiled on all platforms with a decent C compiler (a small amount of porting may be required). It builds and runs out of the box on Linux, FreeBSD, NetBSD, Solaris, OSX, Darwin, and Windows/Cygwin.
- RefDB is modular and accessible. You can plug in a variety of database engines to store your data, and you can choose between a variety of interfaces for interactive work. You can use RefDB in your projects through shell scripts or from Perl programs.
- The RefDB handbook (more than 300 printed pages) helps you to get RefDB up and running quickly and explains how to use the software for both administrators and users in great detail. In addition there is a tutorial targeted at plain users.
- RefDB uses a SQL database engine to store the references, notes, and the bibliography styles. Choose either an external database server for optimum performance and flexibility, or an embedded database engine for convenience (see below for supported database engines).
- Both reference and bibliography style databases use the relational features of SQL databases extensively to consolidate information and to save storage space.
- RefDB employs a three-tier architecture with lots of flexibility: clients, an application server that can run as a daemon, and the database server. If you prefer the embedded SQL engine, therell be a two-tier setup. In both cases, all tiers may run on a single workstation for individual use.
- The application server can generate log messages to monitor its operation.
- RefDB contains two standard interfaces: a command line interface for terminal addicts and for use in scripts, and a PHP-based web interface for a more visual approach. In addition, both Emacs and Vim users can access RefDB from the editing environment theyre used to. Finally, there is also a Perl client module to integrate RefDB functionality into your own Perl programs.
- The main input format for bibliographic data is RIS which can be generated and imported by all major reference databases on Windows (Reference Manager, EndNote and the like). An XML representation of RIS using the risx DTD is also supported as a native format. The latter is well suited as a means to import SGML or XML bibliographic data.
- Import filters are provided for Medline (tagged and XML), BibTeX, MARC, and DocBook.
- The data can be retrieved as simple text, formatted as HTML, formatted as a DocBook bibliography element (SGML or XML), formatted as a TEI listBibl element (XML), formatted as BibTeX reference list, or formatted as RIS or risx files.
- All character encodings supported by your platform can be used both for data input and for data export. This includes European character sets like Latin-1 and of course Unicode.
- Extended notes can be linked to one or more references, authors, periodicals, or keywords to create topics or material collections. These are more powerful and flexible than folder systems and the like.
- The query language is fairly simple yet powerful. You can use booleans to combine queries on any combination of fields. You can use brackets to group queries. You can use Unix-style regular expressions to formulate advanced queries.
Enhancements:
- A problem was fixed with the addref/updateref command, which would occasionally report an error although the command in fact succeeded.
- A possible segfault in the checkref command was fixed too.
- Bibliographies now accept references without any titles.

jwma is a WebMail implementation in Java, enabling the user to access, manage and compose email using a standard web browser. However, jwma is more then that. If you are interested, then read the more detailed overview on the features and use of jwma. Please note that you you might be looking at an offline copy, and that you will always find the latest release version of this documents at http://jwma.sourceforge.net. However, as the online version will reflect the latest release version, it might be better to browse the local version that came with the release you are using.
System administrators that want to enable their users to access, manage and compose email using a standard web browser. jwma offers sufficient features, stability and total control over the look and feel. Especially the latter is supported through jwmas underlying MVC model 2 architecture, and allows to change the "user interface" to the sites needs; very simple and fast.
jwma doesnt represent a shrink-wrapped product. jwma is open-source and can be downloaded and deployed for free. This implies that your expectations might not be met, and it might cost you valuable time to really deploy jwma. However, we are constantly trying to improve jwma and its documentation, and will especially be able to do so if we receive help in form of feedback (hints, configuration examples, source code etc.). The project site on SourceForge offers several ways to do so.
Enhancements:
- added support for IMAP subscription mechanism
- Remember-Me feature on login handling
- Added support for IMAP subscription mechanism
- root folder setting on first time login more failsafe
- Enforcing folder/mailbox sorting
- Last message sort criteria persisted to user preferences
- Added contributed translations for italian and french (might be incomplete).
- Configuration refactored:
- -> Data model for configuration data
- -> support for multiple preconfigured post offices
- -> simplified configuration by moving compile time config
- -> migrated from properties to more structured XML persistent form
- IMAP supscription mechanism supported (including subscribe/unsubscribe)
- root and special folders user configurable
- post office selection on login
- remember me (username and postoffice) for login
- Post office related reply-to domain (-> username@reply-to domain) documentation update

wmhdplop project monitors your hard drives and displays visual information about their activity (read, write, swapin, swapout), and optionally (if hddtemp is running as a daemon), displays their temperature/status.
Main features:
- 0-portability, wont compile/run on anything without a recent kernel (see requirements below)
- useless animation reflecting disc I/O.
- another useless animation reflecting swap activity.
- annoying blinking leds.
- a textual information of your harddrive throughput.
- supports ide drives, and (not 100% sure) scsi and md arrays.
- display of the hd temperature if the hddtemp daemon is running.
Installation:
The `configure shell script attempts to guess correct values for various system-dependent variables used during compilation. It uses those values to create a `Makefile in each directory of the package.
It may also create one or more `.h files containing system-dependent definitions.
Finally, it creates a shell script `config.status that you can run in the future to recreate the current configuration, and a file `config.log containing compiler output (useful mainly for debugging `configure).
It can also use an optional file (typically called `config.cache and enabled with `--cache-file=config.cache or simply `-C) that saves the results of its tests to speed up reconfiguring. (Caching is disabled by default to prevent problems with accidental use of stale cache files.)
If you need to do unusual things to compile the package, please try to figure out how `configure could check whether to do them, and mail diffs or instructions to the address given in the `README so they can be considered for the next release.
If you are using the cache, and at some point `config.cache contains results you dont want to keep, you may remove or edit it.
The file `configure.ac (or `configure.in) is used to create `configure by a program called `autoconf. You only need `configure.ac if you want to change it or regenerate `configure using a newer version of `autoconf.
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.

xpuyopuyo project is a Tetris-like puzzle game with AI.

The object is to match four or more blocks of the same color.

Multiple matches are worth more points, and result in rocks being dumped on the opponent.

It supports human-human, human-AI, AI-AI, or network game play, and a number of gameplay options including themes and music.

The game also features AIs that can learn to play strategically.

Warsync is the program that initiates replication between the Warsync server and its clients. Warsync is designed to be called from the command line of the Warsync server to initiate replication on demand. It can also be called from cron on the server to automate replication.
Warsync not only replicates files from the server to the client, but can also synchronize what software packages are installed on a Debian GNU/Linux system.
Warsync determines what files to replicate by processing the /etc/warsync/filepacks.d directory on the sever. This directory contains filepacks which are simple text files that contain lists of the files and directories that should be replicated.
Installation
On a Debian GNU/Linux system, the best way to install Warsync is to download the Debian package. Once downloaded it can be installed easily with dpkg.
dpkg -i warsync_0.9.8_all.deb
If you receive an error about missing dependencies, a quick call to apt-get will fix that up.
apt-get -f install
Warsync can also be installed manual from the source tarball, although this method has not been tested. A from source installation would go something like this:
tar zxvf warsync_0.9.8.tar.gz
cd warsync-0.9.8
perl Makefile.PL
make
make install
Enhancements:
- Filepack replication introduced.
- Debian package snapshot improvements.
- Output improvments. -q and -v actually mean something along with special handling when run from non-tty (such as cron).
- Real documentation! See warsync-howto manpage.