Free apache 1.3.33 software for linux

apache-top provides real-time display of the active processes from a remote apache server.
With apache-top you can get:
- The active apache processes with their associated PID, the status, the seconds being active, the CPU usage, the asociated VirtualHost, the accessing ip and the request (POST or GET, the file being accessed and the used protocol)
- The server uptime and the last time it was restarted
- The CPU usage
- Requests by second, Kb by second and the average Kb by request
- Number of active and inactive processes
- A graph with the inactive and active processes and their status

Apache Solr is a high performace search server based on Lucene, with XML/HTTP and JSON APIs, hit highlighting, faceted search, caching, replication, and a Web administration interface.
The project is currently under incubation at the Apache Software Foundation.
Instructions for Building Apache Solr
1. Download the J2SE 5.0 JDK (Java Development Kit) or later from http://java.sun.com. You will need the JDK installed, and the %JAVA_HOME%bin directory included on your command path. To test this, issue a "java -version" command from your shell and verify that the Java version is 5.0 or later.
2. Download the Apache Ant binary distribution from http://ant.apache.org. You will need Ant installed and the %ANT_HOME%bin directory included on your command path. To test this, issue a "ant -version" command from your shell and verify that Ant is available.
3. Download the Apache Solr source distribution, linked from the above incubator web site. Expand the distribution to a folder of your choice, e.g. c:solr.
4. Navigate to that folder and issue an "ant" command to see the available options for building, testing, and packaging solr.
Enhancements:
- This is the first release since graduating from the Apache Incubator.
- Some of the new features include CSV/delimited-text data loading, time based autocommit, faster faceting, negative filters, a spell-check handler, sounds-like word filters, regex text filters, and more flexible plugins.

Apache-SSL package offers SSL extensions for Apache.
Apache-SSL is a secure Webserver, based on Apache and SSLeay/OpenSSL. It is licensed under a BSD-style licence, which means, in short, that you are free to use it for commercial or non-commercial purposes, so long as you retain the copyright notices. This is the same licence as used by Apache from version 0.8.15.
Main features:
- Free for both commercial and non-commercial use.
- 128 bit encryption worldwide.
- Client authentication.
- Full source code.
- Modular extension API.

Apache::ePerl is a fast emulated Embedded Perl (ePerl) facility.

SYNOPSIS

# Apaches httpd.conf file
# mandatory: activation of Apache::ePerl
PerlModule Apache::ePerl
< Files ~ "/root/of/webmaster/area/.+.iphtml$" >
Options +ExecCGI
SetHandler perl-script
PerlHandler Apache::ePerl
< /Files >
# optional: configuration of Apache::ePerl
< Perl >
$Apache::ePerl::Config->{BeginDelimiter} = $Apache::ePerl::Config->{EndDelimiter} = !>;
$Apache::ePerl::Config->{CaseDelimiters} = 0;
$Apache::ePerl::Config->{ConvertEntities} = 1;
< /Perl >
# optional: activation of Apache::Status for Apache::ePerl
< Location /perl-status >
Options +ExecCGI
SetHandler perl-script
PerlHandler Apache::Status
< /Location >

This packages provides a handler function for Apache/mod_perl which can be used to emulate the stand-alone Server-Side-Scripting-Language ePerl (see eperl(3) for more details) in a very fast way. This is not a real 100% replacement for nph-eperl because of reduced functionality under some special cases, principal runtime restrictions and speedup decisions. For instance this variant does not (and cannot) provide the SetUID feature of ePerl nor does it check for allowed filename extensions (speedup!), etc. Instead it uses further features like object caching which ePerl does not use.

But the accepted bristled source file format is exactly the same as with the regular ePerl facility, because Apache::ePerl uses the Parse::ePerl package which provides the original ePerl parser and translator. So, any valid ePerl which works under nph-eperl can also be used under Apache::ePerl.

The intent is to use this special variant of ePerl for scripts which are directly under control of the webmaster. In this situation no real security problems exists for him, because all risk is at his own hands. For the average user you should not use Apache::ePerl. Instead additionally install the regular stand-alone ePerl facility (nph-eperl) for those users.

So, the advantage of Apache::ePerl against the regular nph-eperl is better performance and nothing else. Actually scripts executed under Apache::ePerl are at least twice as fast as under nph-eperl. The reason its not that ePerl itself is faster. The reason is the runtime in-core environment of Apache/mod_perl which does not have any forking overhead.

Apache::Storage is Perl module containing simple functions to store and retrieve information from within the Apache process.

Apache Toolbox provides a means to easily compile Apache with SSL, PHP (v4 or v3), MySQL, APC (Alternative PHP Cache), mod_auth_nds, mod_dynvhost, WebDAV, mod_fastcgi, mod_gzip, mod_layout, mod_throttle, mod_accessref, mod_auth_sys, mod_bandwidth, mod_auth_ldap, mod_roaming, mod_perl, Jakarta, OpenLDAP, mod_dtcl, mod_python, mod_frontpage, mod_relocate, mod_backhand, mod_trigger, mod_watch, mod_filter, libcurl for PHP, MING for PHP, mod_auth_mysql, mod_auth_samba, mod_index_rss, mod_random [by Brian Aker], mod_allowdev, mod_auth_cookie, mod_auth_cookie_file, mod_auth_external, mod_auth_inst, mod_auth_system, mod_eaccess, mod_bandwidth, mod_cgisock, mod_urlcount, mod_disallow_id, mod_peephole, mod_put, mod_qs2ssi, mod_session, mod_cvs, mod_macro, mod_random, mod_ip_forwarding, mod_ticket, mod_monitor, jakarta-tomcat, jakarta-ant, jakarta-servletapi, Java Development Kit, Java API for XML Parsing, Java Secure Sockets Extension, mod_pcgi2, apache IPv6 patch, and the latest gd libraries with PNG/JPEG/Freetype2/Zlib support.

You can also hack apaches internal settings so it will report a differnet version of httpd all together, improve your security.

Includes support for mod_access, mod_asis, mod_auth_db, mod_autoindex, mod_digest, mod_example, mod_imap, mod_log_agent, mod_mime, mod_negotiation, mod_setenvif, mod_status, mod_usertrack, mod_actions, mod_auth, mod_auth_dbm, mod_cern_meta, mod_dir, mod_expires, mod_include, mod_log_config, mod_mime_magic, mod_proxy, mod_unique_id, mod_vhost_alias, mod_alias, mod_auth_anon, mod_auth_digest, mod_cgi, mod_env, mod_headers, mod_info, mod_log_referer, mod_mmap_static, mod_rewrite, and mod_speling, which come default with apache.

It is fully customizable and menu driven. Everything is compiled from source. It checks for RPMs that might cause problems and uses wget to automatically download the source if its missing.

Gump is Apaches continuous integration tool. Apache Gump is written in python and fully supports Apache Ant, Apache Maven and other build tools. Gump is unique in that it builds and compiles software against the latest development versions of those projects. This allows gump to detect potentially incompatible changes to that software just a few hours after those changes are checked into the version control system. Notifications are sent to the project team as soon as such a change is detected, referencing more detailed reports available online.

You can set up and run Gump on your own machine and run it on your own projects, however it is currently most famous for building most of Apaches java-based projects and their dependencies (which constitutes several million lines of code split up into hundreds of projects). For this purpose, the gump project maintains its own dedicated server.

How does Gump work?

With Traditional Gump, project definitions are converted from XML to scripts native to the platform on which you are running. With Python Gump the XML is mapped into in memory objects for processing. Scripts execute cvs or svn update commands for every module which contains a project being built, and invoke builds for each project in an order that ensures that dependencies are satisfied. Build outputs are processed and, if successful, dependent projects are then built on these outputs.

The commands use the actual build.xml files from the projects, but do not use the scripts or jar files checked into CVS/SVN. Instead, the CLASSPATH is set and properties are passed on the command line.

Note

Gump sets Ants build.sysclasspath to only and manages the system classpath:
To quote Ant: Only the system classpath is used and classpaths specified in build files, etc are ignored. This situation could be considered as the person running the build file knows more about the environment than the person writing the build file

The net effect is that every project is built every day with the latest version of every dependency - including the latest Ant, latest JUnit, latest XML parser.

The results are captured into html pages that largely are consistent with the style of the Jakarta project. An extensive amount of hypertext links are added to allow quick and easy navigation, and failures are color coded on the main build page.

A Perl script which is driven off of a naglist will optionally send e-mails to various newsgroups upon matching strings being found in the build output. This is typically used to alert developers of build failures.