Free webalizer 2.01 10 software for linux

Webalizer is a fast, free web server log file analysis program. The project produces highly detailed, easily configurable usage reports in HTML format, for viewing with a standard web browser.
It was written to solve several problems that I had with currently available analysis packages. A vast majority of them were written in Perl or some other scripting language, and took forever to run. Some were not free. Some even produced wrong results, or results that were not in a format I found very useful.
In order to get the stats I wanted, in a format that I liked, I wrote The Webalizer, and have made it available here, to anyone who wants it, for any purpose. Starting as a simple Perl script with limited capabilities, it has grown into a full featured, robust and fast analysis tool, being used by thousands of systems around the globe.
Main features:
- Is written in C to be extremely fast and highly portable. On a 200Mhz pentium machine, over 10,000 records can be processed in one second, with a 40 Megabyte file taking roughly 15 seconds (over 150,000 records).
- Supports standard Common Logfile Format server logs. In addition, several variations of the Combined Logfile Format are supported, allowing statistics to be generated for referring sites and browser types as well. Now also has native support for wu-ftpd xferlog FTP and squid log formats as well.
- Generated reports can be configured from the command line, or by use of one or more configuration files. Detailed information on configuration options can be found in the README file, supplied with all distributions.
- Supports multiple languages. Currently, Catalan, Chinese (traditional and simplified), Croatian, Czech, Danish, Dutch, English, Estonian, Finnish, French, Galician, German, Greek, Hungarian, Icelandic, Indonesian, Italian, Japanese, Korean, Latvian, Lithuanian, Malay, Norwegian, Polish, Portuguese (Portugal and Brazil), Romanian, Russian, Serbian, Slovak, Slovene, Spanish, Swedish, Turkish and Ukrainian are available.
- Unlimited log file sizes and partial logs are supported, allowing logs to be rotated as often as needed, and eliminating the need to keep huge monthly files on the system.
- Distributed under the GNU General Public License, complete source code is available, as well as binary distributions for some of the more popular platforms.

Webalizer Xtended is an extension of Webalizer, which adds additional monthly statistics for all "404 Not Found" errors found in your server log-file, including the number of the "404 Not Found" requests and the corresponding 404 URLs.
Webalizer Xtended project also fixes truncated user agent strings in the "User Agents" statistics, so user agent fields can now be grouped more precisely. It is helpful for detecting and correcting broken links or invasion attempts.
Main features:
- Additional monthly statistics for all "404 Not Found" errors found in your server log-file, including the number of the "404 Not Found"-requests and the corresponding 404-URLs
- "404 Not Found" statistics with incremental logfile processing
- Bug-fix for truncated user agent strings in the "User Agents" statistics of Webalizer version 2.01-10 (user agent fields can now be grouped more precisely)
- Bug-fixes for several buffer overflows in the original Webalizer code
Enhancements:
- IPv6 support was added.
- Several third-party patches were implemented.
- General improvements were made, such as an updated "GroupAgent"-list, a "Main"-link for navigation back to the main index, and updated language files.

Geolizer is a patch for Webalizer that uses the GeoIP library to generate faster and more reliable geographic statistics than the default DNS suffix method. It is recommended that DNS reversal be disabled on your HTTP server for improved performance and more accurate statistics. It can be compiled under MinGW/MSYS and features a human-readable transfer size display.
Side effects can be: possibility to compile native Win32 port under MinGW/MSYS and human-readable size display.
"GeoIP is a C library that enables the user to find the country that any IP address or hostname originates from. It uses a file based database that is accurate as of March 2003. This database simply contains IP blocks as keys, and countries as values. This database should be more complete and accurate than using reverse DNS lookups."
And how to port this feature to Webalizer? At users point of view, patched code takes each IP address and discovers its country default suffix. Then, obtained suffix is appended to hostname (somewhat like "127.0.0.1" becoming "127.0.0.1.net"). After this, Webalizer normally processes such host, I mean it finds full country name and accounts stats on it. This is quite abstract, but the real process isnt too far, its just s bit more optimized. Oh, quite forgot it: if processed entry isnt IP address but DNS hostname, Webalizers
default suffix routines are used. This method is less precise, but resolving DNS once again isnt a smart solution.
Enhancements:
- Country flag picture support was added, but needs the flags package from http://flags.blogpotato.de/.
- Country names were updated from the GeoIP source.
- Localization of country names was improved.
- Code cleanups were done.
- The "--enable-geoip" option is now default, as is "--enable-flags".
- The Win32 version now seeks the webalizer.conf file in the executable directory.
- Static binaries are now bound with the GeoIP 1.4.1 library and "GEO-106FREE 20070101 Build 1" database.

wac is free and licensed under the General Public License that you can use it, modify it at your convenience.

If you plan to embed it in a (commercial) package, remember this package has to conform with the General Public License.

Installation:

tar -xzf wac-2.01.tgz
cd wac-2.01
./configure
make
su -c "make install"

rshaper is a Linux kernel module that limits the incoming bandwidth for packets aimed at different hosts.

While the former issue can be addressed with the conventional shaper driver, the latter cant be easily addressed by the standard shaper. As a matter of facts, I have not been able to use the shaper to address the former situation, either; this because effective filtering can only be achieved through source-routing, but when I had to deal with this problem, the shaper only existed for Linux-2.1 while my production setup was constrained to be 2.0. Moreover, with netfilter and rshaper the outgoing traffic can be shaped

While running rshaper with 2.0 and 2.2 requires patching the network driver, the 2.4 "netfilter" feature helps rshaper by avoiding the need to patch the netword driver.

etherdump project is a very small and efficient ethernet sniffer.
EtherDump is a fork by Peter Willis of ipdump2-pre1 (by Christophe Devine) with a few small improvements and feature add-ons with the end result being able to stream raw frames over a network and eventually convert them into pcap format and import into a pcap-reading prog of your choice (I personally love Ethereal).
Pretty simple use; just run the prog with no arguments and you will get the usage instructions. Log a session to a file using ASCII hex dump and when you are done run `text2pcap hex_dump pcap_file and read `pcap_file with Ethereal or another libpcap-aware program.
Since version 2.01 EtherDump supports some minimal packet filtering rules. Some of the rules you can use are "proto" or "protocol", "sport" or "sourceport", "dport" or "destinationport", "src" or "source", and "dst" or "destination". You can also give "!" or "not" to negate a particular rule.
If you execute EtherDump from a symlink named "tcpdump", the default print out method is tcpdump-like.
On uClibc the compiled size is ~8kB so this is very well suited for embedded systems where you want to debug a network interface but dont have room for a whole libpcap+application_layer program. Instead just combine netcat or a CGI script + httpd with EtherDump and read the traffic (converted to pcap) on another machine on the network.
Enhancements:
- Changes by Peter Willis since 2.0:
- Changed configuration option to reflect new name is "etherdump", not "packetdump". -p is now -e.
- Added basic [ipv4] filtering rules.
- Improved tcpdump output.
- If etherdump was run as a program named tcpdump, defaults to tcpdump-like output.
- Added -i to specify interface.
- If EtherDump is executed as "tcpdump", tcpdump-like output is the default output type.

glFTPd is a free FTP server for UNIX based systems. It is highly configurable and its possibilities are endless.
One of the main differences between many other ftp servers and glFTPd is that it has its own user database which can be completely maintained online using ftp site commands. glFTPd runs within a chroot environment which makes it relatively safe.
Main features:
- Virtual users and groups
- Bandwidth throttling (global and per user)
- Upload/Download ratio support
- On the fly CRC calculating of files being uploaded
- Script support on almost all commands and operations
- Online user management (add/remove/edit users using site commands)
- Built-in statistics viewable using site commands
- Encryption support through TLS/SSL integration
- ACL Support
- Many more ...
Enhancements:
- Fix: check return value of fclose when uploading file, somehow NFS likes to fail to close a file
- Fix: when upload error occured do silent zipscript check after the error was sent to client
- Fix: There where some problems with CHOWN when moving files across disks
- Fix: Installer updates by psxc (now it should also work with fedora core 3, which has no `which` command)
- Fix: few small typos in the docs
- Fix: the first abor response line had a multiline-indicator which was wrong
- Change: tls cleanup
- Fix: tls errors will now go to error.log instead of syslog
- Fix: when glftpd will no longer loop it if crashes during logout

AtExit is a Perl module that can perform exit processing for a program or object.

SYNOPSIS

use AtExit;

sub cleanup {
my @args = @_;
print "cleanup() executing: args = @argsn";
}

## Register subroutines to be called when this program exits

$_ = atexit(&cleanup, "This call was registered first");
print "first call to atexit() returned $_n";

$_ = atexit("cleanup", "This call was registered second");
print "second call to atexit() returned $_n";

$_ = atexit("cleanup", "This call shouldve been unregistered by rmexit");
rmexit($_) or warn "couldnt unregister exit-sub $_!";

if (@ARGV == 0) {
## Register subroutines to be called when this lexical scope is exited
my $scope1 = AtExit->new( &cleanup, "Scope 1, Callback 1" );
{
## Do the same for this nested scope
my $scope2 = AtExit->new;
$_ = $scope2->atexit( &cleanup, "Scope 2, Callback 1" );
$scope1->atexit( &cleanup, "Scope 1, Callback 2");
$scope2->atexit( &cleanup, "Scope 2, Callback 2" );
$scope2->rmexit($_) or warn "couldnt unregister exit-sub $_!";

print "*** Leaving Scope 2 ***n";
}
print "*** Finished Scope 2 ***n";
print "*** Leaving Scope 1 ***n";
}
print "*** Finished Scope 1 ***n" if (@ARGV == 0);

END {
print "*** Now performing program-exit processing ***n";
}

The AtExit module provides ANSI-C style exit processing modeled after the atexit function in the standard C library (see atexit(3C)). Various exit processing routines may be registered by calling atexit and passing it the desired subroutine along with any desired arguments. Then, at program-exit time, the subroutines registered with atexit are invoked with their given arguments in the reverse order of registration (last one registered is invoked first). Registering the same subroutine more than once will cause that subroutine to be invoked once for each registration.

An AtExit object can be created in any scope. When invoked as a function, atexit registers callbacks to be executed at program-exit time. But when invoked as an object-method (using the $object->method_name syntax), callbacks registered with an AtExit object are executed at object-destruction time! The rules for order of execution of the registered subroutines are the same for objects during object-destruction, as for the program during program-termination.

The atexit function/method should be passed a subroutine name or reference, optionally followed by the list of arguments with which to invoke it at program/object exit time. Anonymous subroutine references passed to atexit act as "closures" (which are described in perlref). If a subroutine name is specified (as opposed to a subroutine reference) then, unless the subroutine name has an explicit package prefix, it is assumed to be the name of a subroutine in the callers current package. A reference to the specified subroutine is obtained, and, if invocation arguments were specified, it is "wrapped up" in a closure which invokes the subroutine with the specified arguments. The resulting subroutine reference is added to the front of the list of exit-handling subroutines for the program (atexit) or the AtExit object ($exitObject->atexit) and the reference is then returned to the caller (just in case you might want to unregister it later using rmexit. If the given subroutine could not be registered, then the value zero is returned.

The rmexit function/method should be passed one or more subroutine references, each of which was returned by a previous call to atexit. For each argument given, rmexit will look in the list of exit-handling subroutines for the program (rmexit) or the AtExit object ($exitObject->rmexit) and remove the first matching entry from the list. If no arguments are given, then all program or object exit-handlers are unregistered! The value returned will be the number of subroutines that were successfully unregistered.

At object destruction time, the DESTROY{} subroutine in the AtExit module iterates over the subroutine references in the AtExit object and invokes each one in turn (each subroutine is removed from the front of the queue immediately before it is invoked). At program-exit time, the END{} block in the AtExit module iterates over the subroutines in the array returned by the exit_subs method and invokes each one in turn (each subroutine is removed from the front of the queue immediately before it is invoked). Note that in both cases (program-exit, and object-destruction) the subroutines in this queue are invoked in first-to-last order (the reverse order in which they were registered with atexit).