mod log spread2 0.0beta1
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 2037
mod-log-spread2 0.0beta1
mod-log-spread2 is an Apache 2.x module for logging into spread framework. more>>
mod-log-spread2 is an Apache 2.x module for logging into spread framework.
mod-log-spread2 doesnt support fallback hosts, and virtual host groups.
<<lessmod-log-spread2 doesnt support fallback hosts, and virtual host groups.
Download (0.021MB)
Added: 2006-05-31 License: The Apache License 2.0 Price:
1246 downloads
Simple Log 2.0.1
Simple Log is a small library that does logging very simply. more>>
Simple Log is a small library that does logging very simply and requires you to do almost nothing (other than actually logging) to get log output to happen. Simple Log is much simpler to use than a logging framework, especially in terms of configuration.
It doesnt attempt to solve every logging problem in one package, but contains enough features to be a viable alternative for most applications that need logging. This tool will handle the logging needs of most small- to large-sized projects, but with an almost non-existent learning curve.
Enhancements:
- This release is primarily about the addition of log rolling (by time of day, file size, or custom strategy), the inclusion of a small but humorous user guide, the fixing of a raft of minor bugs, and the inclusion of a few other small features increasing flexibility.
<<lessIt doesnt attempt to solve every logging problem in one package, but contains enough features to be a viable alternative for most applications that need logging. This tool will handle the logging needs of most small- to large-sized projects, but with an almost non-existent learning curve.
Enhancements:
- This release is primarily about the addition of log rolling (by time of day, file size, or custom strategy), the inclusion of a small but humorous user guide, the fixing of a raft of minor bugs, and the inclusion of a few other small features increasing flexibility.
Download (0.98MB)
Added: 2006-07-25 License: The Apache License 2.0 Price:
1187 downloads
Nmap Log Stripp3r 1.0
Nmap Log Stripp3r is intended to be a way to condense all, or some, of the IPs of a random nmap scan. more>>
Nmap Log Stripp3r program is intended to be a way to condense all, or some, of the IPs of a "random" nmap scan into a file for later usage.
Common uses are to be able to feed the file back into nmap with the -iL switch, or feeding it into another port or vulnerability scanner of your choice.
Stripp3r supports stripping the nmap log of all but the IPs of hosts running a certain service, a version of a service, or even an arbitrary banner, and writing them to a file.
This is intended to be a way to condense all the IPs of a "random" Nmap scan into a file for later useage. Common uses are to be able to feed the file back into Nmap its self with the -iL switch, or feeding it into another port or vulnerability scanner.
Useage: ./stripp3r < logfile > < output > "< version string >" -v
Pretty simple. First, you must run an Nmap scan, on random hosts.
Ex. nmap -p 80 -sV -v -iR 500000 -oN nmaplogfile.nmap
This will tell nmap to do a scan service scan of 500,000 random IP addresses for the port 80, vobosely, and save the log to a file named nmaplogfile.nmap. You can change this around, eg, scanning a different service port (if say, you were looking for computers running FTP, you would scan for port 21 instead of 80 for HTTP), scanning a different number of hosts (500,000 or so is good, takes a few hours ususally though), or saving the log file to a different filename.
Nmap will then save a list of hosts that were "up" to a log file, with some informaiton about them, specifically weather the port that you specified was open, closed, or filtered. We are interested in "open" ports, so by default, Stripp3r will take all the log
enteries that have the port your specified listed as "open" and condense them into a file, listing only the IPs, one on each line.
Ex. ./stripp3r nmaplogfile.nmap output.ips
You can be more specific, and have Stripp3r put only the IPs that are running a certain service in the output file. The service string will only register the strings matching EXACTLY, so be careful to get the case and such correct.
apache httpd 1.3.27 (wont work)
Apache 1.3.27 (wont work)
Apache httpd 1.3.27 (works!)
Ex. ./stripp3r nmaplogfile.nmap output.ips "Apache httpd 1.3.27"
If you want to try it with verbosity, say
Ex. ./stripp3r nmaplogfile.nmap output.ips "Apache httpd 1.3.27" -v
And stripp3r will print out what it finds, along with writing it to the file.
You may change, copy, and reproduce this file, as long as the author is given credit for the initial writing of the code.
<<lessCommon uses are to be able to feed the file back into nmap with the -iL switch, or feeding it into another port or vulnerability scanner of your choice.
Stripp3r supports stripping the nmap log of all but the IPs of hosts running a certain service, a version of a service, or even an arbitrary banner, and writing them to a file.
This is intended to be a way to condense all the IPs of a "random" Nmap scan into a file for later useage. Common uses are to be able to feed the file back into Nmap its self with the -iL switch, or feeding it into another port or vulnerability scanner.
Useage: ./stripp3r < logfile > < output > "< version string >" -v
Pretty simple. First, you must run an Nmap scan, on random hosts.
Ex. nmap -p 80 -sV -v -iR 500000 -oN nmaplogfile.nmap
This will tell nmap to do a scan service scan of 500,000 random IP addresses for the port 80, vobosely, and save the log to a file named nmaplogfile.nmap. You can change this around, eg, scanning a different service port (if say, you were looking for computers running FTP, you would scan for port 21 instead of 80 for HTTP), scanning a different number of hosts (500,000 or so is good, takes a few hours ususally though), or saving the log file to a different filename.
Nmap will then save a list of hosts that were "up" to a log file, with some informaiton about them, specifically weather the port that you specified was open, closed, or filtered. We are interested in "open" ports, so by default, Stripp3r will take all the log
enteries that have the port your specified listed as "open" and condense them into a file, listing only the IPs, one on each line.
Ex. ./stripp3r nmaplogfile.nmap output.ips
You can be more specific, and have Stripp3r put only the IPs that are running a certain service in the output file. The service string will only register the strings matching EXACTLY, so be careful to get the case and such correct.
apache httpd 1.3.27 (wont work)
Apache 1.3.27 (wont work)
Apache httpd 1.3.27 (works!)
Ex. ./stripp3r nmaplogfile.nmap output.ips "Apache httpd 1.3.27"
If you want to try it with verbosity, say
Ex. ./stripp3r nmaplogfile.nmap output.ips "Apache httpd 1.3.27" -v
And stripp3r will print out what it finds, along with writing it to the file.
You may change, copy, and reproduce this file, as long as the author is given credit for the initial writing of the code.
Download (0.002MB)
Added: 2006-04-17 License: GPL (GNU General Public License) Price:
1286 downloads
Log Mine 0.03
Log Mine is a tool that produces reports on usage patterns on your Web site. more>>
Log Mine is a tool that produces reports on usage patterns on your Web site.
Web server log files are not just hit counters. They contain valuable information about the usage patterns of your website. Unforunately many web log analysis tools lay emphasis on telling you how many hits your site had or how many pages were seen and how many bytes were transferred.
A more usefull statistic would be which percentage of users came to your site went to a product information page, and which percentage of those users hit the checkout button, and which percentage actually completed their order. The trouble is the very nature of the web makes it nearly impossible to get accurate figures for such statistics.
However over periods of time, the errors present average out and it is possible to get a good indication of these ratios by properly mining the log file. That brings us back to square one, how do we get this information with traditional log analysers?
Traditional log analysers will produce weekly, monthly or daily charts for the usage of your site, but rarely do they allow you to create such charts for individual pages or referrrs - something very usefull if you run advertising campaigns on other sites.
Enter Log Mine. This new web log analyser / Mining tool will allow you to create just about any kind of report from the contents of your log file. Log Mine is not concerned about speed and it will be very greedy when it comes to taking up space on your hard disk/database but it will let you change your reporting without having to process gigabytes of log files each time.
Enhancements:
- Importing of Web server log files into the database was simplified.
- Multiple log files can now be processed at once.
- A bug in the monthly report was fixed.
<<lessWeb server log files are not just hit counters. They contain valuable information about the usage patterns of your website. Unforunately many web log analysis tools lay emphasis on telling you how many hits your site had or how many pages were seen and how many bytes were transferred.
A more usefull statistic would be which percentage of users came to your site went to a product information page, and which percentage of those users hit the checkout button, and which percentage actually completed their order. The trouble is the very nature of the web makes it nearly impossible to get accurate figures for such statistics.
However over periods of time, the errors present average out and it is possible to get a good indication of these ratios by properly mining the log file. That brings us back to square one, how do we get this information with traditional log analysers?
Traditional log analysers will produce weekly, monthly or daily charts for the usage of your site, but rarely do they allow you to create such charts for individual pages or referrrs - something very usefull if you run advertising campaigns on other sites.
Enter Log Mine. This new web log analyser / Mining tool will allow you to create just about any kind of report from the contents of your log file. Log Mine is not concerned about speed and it will be very greedy when it comes to taking up space on your hard disk/database but it will let you change your reporting without having to process gigabytes of log files each time.
Enhancements:
- Importing of Web server log files into the database was simplified.
- Multiple log files can now be processed at once.
- A bug in the monthly report was fixed.
Download (0.029MB)
Added: 2006-05-04 License: MPL (Mozilla Public License) Price:
1271 downloads
mod_log50x 1.0
mod_log50x Apache module logs error 500 - 509 to logfiles. more>>
mod_log50x Apache module logs error 500 - 509 to logfiles. It enables you to log all error 50x status responses to logfiles.
How:
1. Either compile a apache module from the sources, or get a binary release.
2. Copy the module in the modules directory of your apache server.
3. Modify your httpd.conf to load the module:
LoadModule log50x_module modules/mod_log50x.so
4. Specify what errors should be logged in which logfile in your httpd.conf
Log50xFile /var/log/webserver50x.log
Log500File /var/log/webserver500.log
Log501File /var/log/webserver501.log
Log502File /var/log/webserver502.log
Log503File /var/log/webserver503.log
Log504File /var/log/webserver504.log
Log505File /var/log/webserver505.log
Log506File /var/log/webserver506.log
Log507File /var/log/webserver507.log
Log508File /var/log/webserver508.log
Log509File /var/log/webserver509.log
5. Restart your apache webserver
Details on the configuration options:
The Log50xFile specifies in which file all error in the range 500 - 509 should be logged.
The Log500File specifies in which file all error 500 should be logged.
The Log501File specifies in which file all error 501 should be logged.
etc.
The Log509File specifies in which file all error 509 should be logged.
It is possible to specify the same logfile multiple times, so this configuration results in all error 500 and 501 beeing logged in the same file.
Log500File /var/log/webserver500_501.log
Log501File /var/log/webserver500_501.log
When you specify the following configuration, then all error 500-509 are logged to the webserver50x logfile.
In addition to this, all error 500 are logged to the webserver500.log file.
Log50xFile /var/log/webserver50x.log
Log500File /var/log/webserver500.log
<<lessHow:
1. Either compile a apache module from the sources, or get a binary release.
2. Copy the module in the modules directory of your apache server.
3. Modify your httpd.conf to load the module:
LoadModule log50x_module modules/mod_log50x.so
4. Specify what errors should be logged in which logfile in your httpd.conf
Log50xFile /var/log/webserver50x.log
Log500File /var/log/webserver500.log
Log501File /var/log/webserver501.log
Log502File /var/log/webserver502.log
Log503File /var/log/webserver503.log
Log504File /var/log/webserver504.log
Log505File /var/log/webserver505.log
Log506File /var/log/webserver506.log
Log507File /var/log/webserver507.log
Log508File /var/log/webserver508.log
Log509File /var/log/webserver509.log
5. Restart your apache webserver
Details on the configuration options:
The Log50xFile specifies in which file all error in the range 500 - 509 should be logged.
The Log500File specifies in which file all error 500 should be logged.
The Log501File specifies in which file all error 501 should be logged.
etc.
The Log509File specifies in which file all error 509 should be logged.
It is possible to specify the same logfile multiple times, so this configuration results in all error 500 and 501 beeing logged in the same file.
Log500File /var/log/webserver500_501.log
Log501File /var/log/webserver500_501.log
When you specify the following configuration, then all error 500-509 are logged to the webserver50x logfile.
In addition to this, all error 500 are logged to the webserver500.log file.
Log50xFile /var/log/webserver50x.log
Log500File /var/log/webserver500.log
Download (0.007MB)
Added: 2006-05-10 License: The Apache License Price:
1262 downloads
Build Log 0.0.3
Build Log is a tool to log software builds. more>>
Buildog was inspired by my need to track the steps involved in software builds. Particularly the software packages in the Linux From Scratch book.
It is not a package manager in the traditional sense, it will not track dependences. It tries to stay out of your way as much as possible.
If you grow weary of RPM spec files, or this months "package manager" (there are about a dozen or so of them out there, with new distributions adding their own every month) Buildog may be for you.
What it will do for you is log the information required to build it, files it created, URLs it needs (it will fetch them for you too if you want, with support for mirrors and caching) a log of the build stages, notes and descriptions, its home page, and any other information you may wish to add.
Its pretty simple to use, if youve ever installed packages from source, youll get the hang if it quickly.
Installation
Quite a bit of work has gone into making this install nicely. Perl programs are kind of notorious for being difficult to install.
It uses the autoconf to guess your location of perl, supports the usual --prefix --bindir --sysconfdir and --localstatedir options. Type make install to install it, (a plain make shows what will be installed where).
<<lessIt is not a package manager in the traditional sense, it will not track dependences. It tries to stay out of your way as much as possible.
If you grow weary of RPM spec files, or this months "package manager" (there are about a dozen or so of them out there, with new distributions adding their own every month) Buildog may be for you.
What it will do for you is log the information required to build it, files it created, URLs it needs (it will fetch them for you too if you want, with support for mirrors and caching) a log of the build stages, notes and descriptions, its home page, and any other information you may wish to add.
Its pretty simple to use, if youve ever installed packages from source, youll get the hang if it quickly.
Installation
Quite a bit of work has gone into making this install nicely. Perl programs are kind of notorious for being difficult to install.
It uses the autoconf to guess your location of perl, supports the usual --prefix --bindir --sysconfdir and --localstatedir options. Type make install to install it, (a plain make shows what will be installed where).
Download (0.040MB)
Added: 2005-04-04 License: LGPL (GNU Lesser General Public License) Price:
1664 downloads
DKP Log Parser 1.4.1
DKP Log Parser (DKPLP) is a tool designed to help administrate time-based and/or event-based DKP reward system. more>>
DKP Log Parser (DKPLP) is a tool designed to help administrate time-based and/or event-based DKP reward system in conjunction with EQDKP (or any other DKP software implementing a required interface). The project is configurable to be compatible with any game that produces any kind of log. There are currently predefined pattern sets for EverQuest, EverQuest2 and World of Warcraft (with CT RaidTracker). If you are playing another game then you can either write new patterns for it yourself, or ask the the forum (be sure to include a sample log though).
DKP Log Parsers goal is to reduce the administrative overhead of running complex DKP reward system, by parsing the logs, calculating the DKP per person and sending the results (the loot, raids, participants and DKP) directly to EQDKP (or other DKP software). Its widely configurable, allowing it to be used by the many variations of zero-sum and time-based DKP around.
Overview of how DKP Log Parser is used
DKP Log Parser is a software program run on a users desktop (Windows or Unix). It reads in the contents of a game log once a raid has been completed, parses all the information and displays the data for administrators to edit. Once happy with the information, the administrator uploads the data from their PC to the DKP Log Parser plugin on an EQDKP webserver (or any other server implementing the required DKPLP interface), where it can be viewed by all members of the DKP system.
Main features:
- Inbuilt support for Everquest, Everquest II, World of Warcrafts CT RaidTracker plugin, and Ventrilo.
- Extensible enough to be able to handle most logs.
- Time based dkp:
- Accrue DKP by minute, by interval, by event or by a combination of these.
- Zero-sum DKP can be enabled (by minute or by interval) or disabled.
- Tag certain intervals as being more or less important by using weightings to adjust the DKP.
- Data export:
- Upload data to for example EQDKP, select from a number of different data representations.
- Export to plain text
- Export to BB forum markup
- Export to wiki markup
- Export to XML
- Member list and alt character list synchronises with server, making it easy to share setups with other users.
- Optional autocompletion database to remember item names and values between sessions.
- Preprocessors available to perform other operations on the log file. The skys the limit!
<<lessDKP Log Parsers goal is to reduce the administrative overhead of running complex DKP reward system, by parsing the logs, calculating the DKP per person and sending the results (the loot, raids, participants and DKP) directly to EQDKP (or other DKP software). Its widely configurable, allowing it to be used by the many variations of zero-sum and time-based DKP around.
Overview of how DKP Log Parser is used
DKP Log Parser is a software program run on a users desktop (Windows or Unix). It reads in the contents of a game log once a raid has been completed, parses all the information and displays the data for administrators to edit. Once happy with the information, the administrator uploads the data from their PC to the DKP Log Parser plugin on an EQDKP webserver (or any other server implementing the required DKPLP interface), where it can be viewed by all members of the DKP system.
Main features:
- Inbuilt support for Everquest, Everquest II, World of Warcrafts CT RaidTracker plugin, and Ventrilo.
- Extensible enough to be able to handle most logs.
- Time based dkp:
- Accrue DKP by minute, by interval, by event or by a combination of these.
- Zero-sum DKP can be enabled (by minute or by interval) or disabled.
- Tag certain intervals as being more or less important by using weightings to adjust the DKP.
- Data export:
- Upload data to for example EQDKP, select from a number of different data representations.
- Export to plain text
- Export to BB forum markup
- Export to wiki markup
- Export to XML
- Member list and alt character list synchronises with server, making it easy to share setups with other users.
- Optional autocompletion database to remember item names and values between sessions.
- Preprocessors available to perform other operations on the log file. The skys the limit!
Download (4.2MB)
Added: 2007-06-28 License: GPL (GNU General Public License) Price:
850 downloads
Log::StdLog 0.0.3
Log::StdLog is a Perl module with a simple log file via a special filehandle. more>>
Log::StdLog is a Perl module with a simple log file via a special filehandle.
SYNOPSIS
use Log::StdLog { level => warn, file => "$0.log" };
# Messages at the same or a higher level are logged...
print {*STDLOG} error => "This error message will be loggedn";
print {*STDLOG} warn => "This warning message will be loggedn";
# Messages at a lower level are ignored...
print {*STDLOG} info => "This info message will NOT be loggedn";
# The default message level is the one that was specified
# when the module was loaded...
print {*STDLOG} "This is a warning message. It will be loggedn";
This module provides a very simple kind of log file, with a very simple interface. Messages are logged simply by printing to *STDLOG, which the module exports to any namespace into which its loaded.
<<lessSYNOPSIS
use Log::StdLog { level => warn, file => "$0.log" };
# Messages at the same or a higher level are logged...
print {*STDLOG} error => "This error message will be loggedn";
print {*STDLOG} warn => "This warning message will be loggedn";
# Messages at a lower level are ignored...
print {*STDLOG} info => "This info message will NOT be loggedn";
# The default message level is the one that was specified
# when the module was loaded...
print {*STDLOG} "This is a warning message. It will be loggedn";
This module provides a very simple kind of log file, with a very simple interface. Messages are logged simply by printing to *STDLOG, which the module exports to any namespace into which its loaded.
Download (0.007MB)
Added: 2007-01-13 License: Perl Artistic License Price:
1014 downloads
Log Watcher 0.4.1
Log Watcher colorize a system logs for easier reading. more>>
Log Watcher is a tool for log watching and colorize.
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, a file `config.cache that saves the results of its tests to speed up
reconfiguring, and a file `config.log containing compiler output (useful mainly for debugging `configure).
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 at some point `config.cache contains results you dont want to keep, you may remove or edit it.
The file `configure.in is used to create `configure by a program called `autoconf. You only need `configure.in 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.
Enhancements:
- manual typos
- change defaults in config file
- minor changes needed to build on OpenBSD
- fixed lwatch crashes for some spurious configuration
<<lessInstallation:
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, a file `config.cache that saves the results of its tests to speed up
reconfiguring, and a file `config.log containing compiler output (useful mainly for debugging `configure).
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 at some point `config.cache contains results you dont want to keep, you may remove or edit it.
The file `configure.in is used to create `configure by a program called `autoconf. You only need `configure.in 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.
Enhancements:
- manual typos
- change defaults in config file
- minor changes needed to build on OpenBSD
- fixed lwatch crashes for some spurious configuration
Download (0.14MB)
Added: 2005-10-19 License: GPL (GNU General Public License) Price:
1466 downloads
mod-vhost-ldap 1.0
mod-vhost-ldap is an Apache 2.x module for storing and configuring virtual hosts from LDAP. more>>
mod-vhost-ldap is an Apache 2.x module for storing and configuring virtual hosts from LDAP. mod-vhost-ldap project supports DocumentRoot, ScriptAlias, ServerName, ServerAlias, ServerAdmin, and SuexecUserGroup directives.
Its built on top of mod_ldap, so it uses its caching capabilities and can be used with a threaded Apache httpd.
<<lessIts built on top of mod_ldap, so it uses its caching capabilities and can be used with a threaded Apache httpd.
Download (0.007MB)
Added: 2006-01-31 License: The Apache License 2.0 Price:
1365 downloads
Strato Log Download 1.2
Strato Log Download is a small Perl script intended to download logfiles from Web accounts from Strato hosted sites. more>>
Strato Log Download is a small Perl script intended to download logfiles from Web accounts from Strato hosted sites.
The problem is that the normal download interface is interactive, and that only about six weeks are kept on the server. So without scripting, youre likely to lose valuable log information (at least I was unable and unwilling to remember to download the logfiles once every six weeks).
This script logs in via the SSL-encrypted web-interface and downloads the files without needing a web-browser (proxies are configurable via the https_proxy environment variable).
Note: For SSL support, you might need additional Perl modules since some distros dont include crypto stuff: either use IO::Socket::SSL or Net::SSL (in Crypt::SSLeay).
If an SSL module is missing, https access will not work.
Usage is very easy:
$ get-logfiles -p mypassword www.mysite.de > logfile.gz
Enhancements:
- Feature: a new logfile download protocol was necessary, because the web interface changed (thanks to J. Puchalla for telling me -- it would probably have gone unnoticed otherwise).
<<lessThe problem is that the normal download interface is interactive, and that only about six weeks are kept on the server. So without scripting, youre likely to lose valuable log information (at least I was unable and unwilling to remember to download the logfiles once every six weeks).
This script logs in via the SSL-encrypted web-interface and downloads the files without needing a web-browser (proxies are configurable via the https_proxy environment variable).
Note: For SSL support, you might need additional Perl modules since some distros dont include crypto stuff: either use IO::Socket::SSL or Net::SSL (in Crypt::SSLeay).
If an SSL module is missing, https access will not work.
Usage is very easy:
$ get-logfiles -p mypassword www.mysite.de > logfile.gz
Enhancements:
- Feature: a new logfile download protocol was necessary, because the web interface changed (thanks to J. Puchalla for telling me -- it would probably have gone unnoticed otherwise).
Download (0.006MB)
Added: 2005-10-24 License: Freely Distributable Price:
1460 downloads
Log::Localized 0.05
Log::Localized is a Perl module to localize your logging. more>>
Log::Localized is a Perl module to localize your logging.
SYNOPSIS
What you most probably want to do is something like:
package Foo;
use Log::Localized;
sub bar {
# this message will be displayed if method bars verbosity is >= 1
llog(1,"running bar()");
}
# this message will be displayed if package Foos verbosity is >= 3
llog(3,"loaded package Foo");
Then paste the following local verbosity rules in a file called verbosity.conf, in the same directory as your program:
# log everything from wherever inside Foo and its subclasses, up to level 3
Foo:: = 3
# except for function Foo::foo who shall have verbosity 0
Foo::bar = 0
SYNOPSIS - ADVANCED
In a program accepting command line arguments, you may want to do:
use Getopt::Long;
use Log::Localized log => 1;
GetOptions("verbose|v+" => sub { $Log::Localized::VERBOSITY++; } );
llog(1,"you used -v");
llog(2,"you used -v -v");
You may alter local verbosity from within the running code:
package Foo;
use Log::Localized log => 1;
# verbosity level is 0 by default
{
# set verbosity locally in this block
local $Log::Debug::VERBOSITY = 5;
llog(5,"this will be logged");
}
debug(5,"but this wont");
If you want to import llog under another name in the calling module:
package Foo;
use Log::Localized rename => "my_log";
# call Log::Localized::llog()
my_log(1,"renamed llog()");
See the examples directory in the module distribution for more real life examples.
Log::Localized provides you with an interface for defining dynamically exactly which part of your code should log messages and with which verbosity.
Log::Localized addresses one issue of traditional logging: in very large systems, a slight increase in logging verbosity usually generates insane amounts of logs. Hence the need of being able to turn on verbosity selectively in some areas of code only, in a localized way.
Log::Localized is based on the concept of local verbosity. Each package and each function in a package has its own local verbosity, set to 0 by default. With Log::Localized you can change the local verbosity in just a function, just a package or just a class hierarchy via a so called verbosity rule. Verbosity rules are passed to Log::Localized either via a configuration file or via an import parameter. By changing verbosity rules according to the needs of the moment, you can alter your programs logging flow in a very fine-grained way, and get logs from only the code areas you are interested in.
Log::Localized comes with default settings that make it usable out of the box, but its configuration options will let you redefine pretty much everything in its behavior.
The actual logging in Log::Localized is handled by Log::Dispatch.
<<lessSYNOPSIS
What you most probably want to do is something like:
package Foo;
use Log::Localized;
sub bar {
# this message will be displayed if method bars verbosity is >= 1
llog(1,"running bar()");
}
# this message will be displayed if package Foos verbosity is >= 3
llog(3,"loaded package Foo");
Then paste the following local verbosity rules in a file called verbosity.conf, in the same directory as your program:
# log everything from wherever inside Foo and its subclasses, up to level 3
Foo:: = 3
# except for function Foo::foo who shall have verbosity 0
Foo::bar = 0
SYNOPSIS - ADVANCED
In a program accepting command line arguments, you may want to do:
use Getopt::Long;
use Log::Localized log => 1;
GetOptions("verbose|v+" => sub { $Log::Localized::VERBOSITY++; } );
llog(1,"you used -v");
llog(2,"you used -v -v");
You may alter local verbosity from within the running code:
package Foo;
use Log::Localized log => 1;
# verbosity level is 0 by default
{
# set verbosity locally in this block
local $Log::Debug::VERBOSITY = 5;
llog(5,"this will be logged");
}
debug(5,"but this wont");
If you want to import llog under another name in the calling module:
package Foo;
use Log::Localized rename => "my_log";
# call Log::Localized::llog()
my_log(1,"renamed llog()");
See the examples directory in the module distribution for more real life examples.
Log::Localized provides you with an interface for defining dynamically exactly which part of your code should log messages and with which verbosity.
Log::Localized addresses one issue of traditional logging: in very large systems, a slight increase in logging verbosity usually generates insane amounts of logs. Hence the need of being able to turn on verbosity selectively in some areas of code only, in a localized way.
Log::Localized is based on the concept of local verbosity. Each package and each function in a package has its own local verbosity, set to 0 by default. With Log::Localized you can change the local verbosity in just a function, just a package or just a class hierarchy via a so called verbosity rule. Verbosity rules are passed to Log::Localized either via a configuration file or via an import parameter. By changing verbosity rules according to the needs of the moment, you can alter your programs logging flow in a very fine-grained way, and get logs from only the code areas you are interested in.
Log::Localized comes with default settings that make it usable out of the box, but its configuration options will let you redefine pretty much everything in its behavior.
The actual logging in Log::Localized is handled by Log::Dispatch.
Download (0.019MB)
Added: 2007-01-23 License: Perl Artistic License Price:
1004 downloads
Log::Dispatch::Atom 0.03
Log::Dispatch::Atom is a Perl module to log to an atom feed. more>>
Log::Dispatch::Atom is a Perl module to log to an atom feed.
SYNOPSIS
use Log::Dispatch::Atom;
my $log = Log::Dispatch::Atom->new(
name => foo,
min_level => debug,
file => file.atom
);
$log->log_message( level => error, message => A problem happened );
$log->log_message( level => debug, message => Got Here );
This class implements logging backed by an Atom feed so that you can subscribe to the errors produced by your application.
You should not use this object directly, but should manage it via a Log::Dispatch object.
IMPLEMENTATION NOTES
In order to safely write to the log file, the entire file must be locked each time that an entry is logged. This probably makes it unsuitable for high volume log files.
The log file is opened and closed on each call to log_message().
METHODS
new()
Takes a hash of arguments. Returns a new Log::Dispatch::Atom object. The following parameters are used:
name [mandatory]
The name of the logging object.
min_level [mandatory]
The minimum logging level this object will accept. See Log::Dispatch for more information.
max_level [optional]
The maximum logging level this object will accept. See Log::Dispatch for more information. The default is the highest possible level (ie: no maximum).
file [mandatory]
Specifies the location of the file to read/write the feed from.
feed_id [optional]
Specifies the identity of the feed itself. Normally, this should be set to the published URI of the feed.
If not specified, it will be omitted, which is in violation of the Atom specification. For more information, see http://www.atomenabled.org/developers/syndication/#requiredFeedElements.
feed_title [optional]
The title of the feed. This should probably be set to the name of your application.
If not specified, it will be omitted, which is in violation of the Atom specification. For more information, see http://www.atomenabled.org/developers/syndication/#requiredFeedElements.
XXX This should probably just use the name parameter. What do you think? Let me know.
feed_author [optional]
The author details of a feed. This is specified as a hash reference, which must contain one or more of the three keys name, email and uri.
In order to create a valid Atom feed, you must either supply an author in every single entry (log message), or ensure that the feed itself has an author. The latter is probably the easier solution, so I recommend this parameter be supplied.
NB: The feed_* parameters will only be used when a new feed is being created. If you are creating a new object for an existing feed, they will be ignored.
log_message()
Takes a hash of arguments. Has no return value. The following parameters are used.
message [mandatory]
The actual log message.
level [mandatory]
The level of the message. See Log::Dispatch for a full list.
id [optional]
Each entry requires an id in order for the feed as a whole to be a valid Atom document. Its used by readers of Atom documents to determine whether or not an entry has been seen previously.
If not specified, this will default to an URL comprising the current time plus the pid plus the hostname plus a monotonically increasing integer. eg: tag:fred.example.com,2005-12-07:1133946771/20827/2. This should be good enough for a uniqueness test.
author [optional]
You can specify author details for an individual entry if desired. The author parameter is expected to be a hash reference, which must contain one or more of the keys name, email or uri.
<<lessSYNOPSIS
use Log::Dispatch::Atom;
my $log = Log::Dispatch::Atom->new(
name => foo,
min_level => debug,
file => file.atom
);
$log->log_message( level => error, message => A problem happened );
$log->log_message( level => debug, message => Got Here );
This class implements logging backed by an Atom feed so that you can subscribe to the errors produced by your application.
You should not use this object directly, but should manage it via a Log::Dispatch object.
IMPLEMENTATION NOTES
In order to safely write to the log file, the entire file must be locked each time that an entry is logged. This probably makes it unsuitable for high volume log files.
The log file is opened and closed on each call to log_message().
METHODS
new()
Takes a hash of arguments. Returns a new Log::Dispatch::Atom object. The following parameters are used:
name [mandatory]
The name of the logging object.
min_level [mandatory]
The minimum logging level this object will accept. See Log::Dispatch for more information.
max_level [optional]
The maximum logging level this object will accept. See Log::Dispatch for more information. The default is the highest possible level (ie: no maximum).
file [mandatory]
Specifies the location of the file to read/write the feed from.
feed_id [optional]
Specifies the identity of the feed itself. Normally, this should be set to the published URI of the feed.
If not specified, it will be omitted, which is in violation of the Atom specification. For more information, see http://www.atomenabled.org/developers/syndication/#requiredFeedElements.
feed_title [optional]
The title of the feed. This should probably be set to the name of your application.
If not specified, it will be omitted, which is in violation of the Atom specification. For more information, see http://www.atomenabled.org/developers/syndication/#requiredFeedElements.
XXX This should probably just use the name parameter. What do you think? Let me know.
feed_author [optional]
The author details of a feed. This is specified as a hash reference, which must contain one or more of the three keys name, email and uri.
In order to create a valid Atom feed, you must either supply an author in every single entry (log message), or ensure that the feed itself has an author. The latter is probably the easier solution, so I recommend this parameter be supplied.
NB: The feed_* parameters will only be used when a new feed is being created. If you are creating a new object for an existing feed, they will be ignored.
log_message()
Takes a hash of arguments. Has no return value. The following parameters are used.
message [mandatory]
The actual log message.
level [mandatory]
The level of the message. See Log::Dispatch for a full list.
id [optional]
Each entry requires an id in order for the feed as a whole to be a valid Atom document. Its used by readers of Atom documents to determine whether or not an entry has been seen previously.
If not specified, this will default to an URL comprising the current time plus the pid plus the hostname plus a monotonically increasing integer. eg: tag:fred.example.com,2005-12-07:1133946771/20827/2. This should be good enough for a uniqueness test.
author [optional]
You can specify author details for an individual entry if desired. The author parameter is expected to be a hash reference, which must contain one or more of the keys name, email or uri.
Download (0.007MB)
Added: 2007-02-09 License: Perl Artistic License Price:
987 downloads
Visitors Web Log Analyzer 0.61
Visitors is a very fast Web log analyzer. more>>
Visitors is a very fast web log analyzer for Linux, Windows, and other Unix-like operating systems. It takes as input a web server log file, and outputs statistics in form of different reports. The design principles are very different compared to other software of the same type:
No installation required, can process up to 150,000 lines of log entries per second in fast computers (20MB/s with my log files average length).
Designed to be executed by the command line, output html and text reports. The text report can be used in pipe to less to check web stats from ssh.
Support for real time statistics with the Visitors Stream Mode introduced with version 0.3.
To specify the log format is not needed at all. Works out of box with apache and most other web servers with a standard log format (see the documentation for more information on the format).
Its a portable C program, can be compiled on many different systems. Binaries for Windows systems are in the Download section of this page.
The produced html report doesnt contain images or external CSS, is self-contained, you can send it by email to users.
Visitors is free software (and of course, freeware), under the terms of the GPL license. You dont need to pay to use it. Visitors is supported, if you want a custom version made directly by the original author for a modest price, contact me at antirez (at) invece.org. ISPs may take advantage of the high processing speed.
Main features:
- Requested pages.
- Requested images.
- Referers by hits and age.
- Unique visitors in each day.
- Page views per visit.
- Pages accessed by the Google crawler (and the date of googles last access on every page).
- Percentage of visits originated from Google searches for every day.
- Users navigation patterns (web trails).
- Keyphrases used in Google searches.
- User agents.
- Weekdays and Hours distributions of accesses.
- Weekdays/Hours combined bidimentional map.
- Month/Year combined bidimentional map.
- Visual path analysis with Graphviz.
- Operating systems, browsers and domains popularity.
- 404 errors.
Enhancements:
- This release adds an important bugfix in the unique visitors algorithm.
- The output is now nearer to reality (though unique visitors stats are always a guess without the use of a cookie).
<<lessNo installation required, can process up to 150,000 lines of log entries per second in fast computers (20MB/s with my log files average length).
Designed to be executed by the command line, output html and text reports. The text report can be used in pipe to less to check web stats from ssh.
Support for real time statistics with the Visitors Stream Mode introduced with version 0.3.
To specify the log format is not needed at all. Works out of box with apache and most other web servers with a standard log format (see the documentation for more information on the format).
Its a portable C program, can be compiled on many different systems. Binaries for Windows systems are in the Download section of this page.
The produced html report doesnt contain images or external CSS, is self-contained, you can send it by email to users.
Visitors is free software (and of course, freeware), under the terms of the GPL license. You dont need to pay to use it. Visitors is supported, if you want a custom version made directly by the original author for a modest price, contact me at antirez (at) invece.org. ISPs may take advantage of the high processing speed.
Main features:
- Requested pages.
- Requested images.
- Referers by hits and age.
- Unique visitors in each day.
- Page views per visit.
- Pages accessed by the Google crawler (and the date of googles last access on every page).
- Percentage of visits originated from Google searches for every day.
- Users navigation patterns (web trails).
- Keyphrases used in Google searches.
- User agents.
- Weekdays and Hours distributions of accesses.
- Weekdays/Hours combined bidimentional map.
- Month/Year combined bidimentional map.
- Visual path analysis with Graphviz.
- Operating systems, browsers and domains popularity.
- 404 errors.
Enhancements:
- This release adds an important bugfix in the unique visitors algorithm.
- The output is now nearer to reality (though unique visitors stats are always a guess without the use of a cookie).
Download (0.11MB)
Added: 2005-11-05 License: GPL (GNU General Public License) Price:
1458 downloads
StandAloneQ3 0.1
StandAloneQ3 is a modified version of the GPL engine of Quake3. more>>
StandAloneQ3 is a modified version of the GPL engine of Quake3 which allows the player to start mods without the need of the Quake3 original CD
StandAloneQ3 is free software released under the GPL license.
To run saq3 you need to launch the mod from the command line like that:
- for windows: quake3.exe +set sf_name fname
- for linux: quake3 +set sf_name fname
Where fname is the folder name of the mod you want to run.
Known working mods are:
- World of Pandam ( http://www.worldofpadman.com/ )
- Western Quake 3 ( http://www.westernquake3.net/ )
If most of the mods will run, some shaders and/or textures used by mods may be missing, displaying errors in the game window.
When the game and maps are loaded missing textures/shaders are logged in the file "missing_shader-textures.log".
It has been reported that using the "pak0.pk3" file provided in Quake3 Arena Demo ( you need to create the folder "baseq3" in the software directory then copy pak0.pk3 in) may solve most of the shader/texture problems found in several mods and will allow bots to work.
In fact, any .pk3 file you have obtained legally can be added in baseq3 folder to complete missing textures or shaders. You must increment pak number every time you add a new one (pak0.pk3, pak1.pk3, pak2.pk3, etc... )
Quake, Quake 3 and Quake 3 Arena are trade marks of Id Software.
<<lessStandAloneQ3 is free software released under the GPL license.
To run saq3 you need to launch the mod from the command line like that:
- for windows: quake3.exe +set sf_name fname
- for linux: quake3 +set sf_name fname
Where fname is the folder name of the mod you want to run.
Known working mods are:
- World of Pandam ( http://www.worldofpadman.com/ )
- Western Quake 3 ( http://www.westernquake3.net/ )
If most of the mods will run, some shaders and/or textures used by mods may be missing, displaying errors in the game window.
When the game and maps are loaded missing textures/shaders are logged in the file "missing_shader-textures.log".
It has been reported that using the "pak0.pk3" file provided in Quake3 Arena Demo ( you need to create the folder "baseq3" in the software directory then copy pak0.pk3 in) may solve most of the shader/texture problems found in several mods and will allow bots to work.
In fact, any .pk3 file you have obtained legally can be added in baseq3 folder to complete missing textures or shaders. You must increment pak number every time you add a new one (pak0.pk3, pak1.pk3, pak2.pk3, etc... )
Quake, Quake 3 and Quake 3 Arena are trade marks of Id Software.
Download (7.5MB)
Added: 2006-01-11 License: GPL (GNU General Public License) Price:
1383 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above mod log spread2 0.0beta1 search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
