|
|
LiteSpeed
| |
| Home Page : |
http://litespeedtech.com |
| Changelog : |
http://litespeedtech.com/changelog.html |
| Screenshot : |
http://litespeedtech.com/images/home/home.gif |
Features
|
| |
LiteSpeed web server is a high performance, secure and easy-to-use web server.
It can handle thousands of concurrent connections with small memory footprint.
It is less vulnerable when facing various attacks.
|
| |
LiteSpeed Web Server supports:
|
| |
| HTTP/1.1 |
| - Backward compatible with HTTP/1.0 |
| - Chunked Transfer Encoding |
| - Basic Authentication |
| - Entity Tag |
| - Range/Multi-range Request |
| - Static and dynamic content compression(gzip) |
| The following features will be supported in the near future: |
| - Multi-Language/Content Negotiation |
| - Digest Authentication |
|
| |
| Dynamic Content Generation |
| - CGI/1.1 |
| - Fast CGI |
| - PHP (through Fast CGI interface) |
| - JSP/Servlet (interface to back-end Servlet engine) |
|
| |
| Virtual Hosting |
| - Supports IP based and name based virtual hosting |
|
| |
| .htaccess Support |
| - Distributed per-directory Access Control and Authentication configuration. |
|
| |
| Security |
| - Secure HTTP (HTTPS): supports SSLv2, SSLv3 and TLSv1 |
| - Access Control at server, virtual host and directory (context) level |
| - File system protection |
| - HTTP Authentication |
| - IP level throttling |
| - Comprehensive IP level connection accounting |
| - Strict HTTP request checking |
| - Comprehensive protection for static files |
| - External application firewall for dynamic content |
| - CGI resources consumption limit |
| - Chroot [Professional Edition only] |
|
| |
| Reliability |
| - Instant recovery maximizes up-time |
| - Runs completely in user space, OS reliability is not affected |
- CGI, Fast CGI and servlet engine run in their standalone processes,
the reliability of the web server is not affected by third party software. |
|
APACHE WEBSERVER
What IS the Apache HTTP Server Project? |
The Apache Project is a collaborative software development effort aimed at creating a robust, commercial-grade, featureful, and freely-available source code implementation of an HTTP (Web) server. The project is jointly managed by a group of volunteers located around the world, using the Internet and the Web to communicate, plan, and develop the server and its related documentation. These volunteers are known as the Apache Group. In addition, hundreds of users have contributed ideas, code, and documentation to the project. This file is intended to briefly describe the history of the Apache Group and recognize the many contributors
. |
| How Apache Came to Be |
In February of 1995, the most popular server software on the Web was the public domain HTTP daemon developed by Rob McCool at the National Center for Supercomputing Applications, University of Illinois, Urbana-Champaign. However, development of that httpd had stalled after Rob left NCSA in mid-1994, and many webmasters had developed their own extensions and bug fixes that were in need of a common distribution. A small group of these webmasters, contacted via private e-mail, gathered together for the purpose of coordinating their changes (in the form of "patches"). Brian Behlendorf and Cliff Skolnick put together a mailing list, shared information space, and logins for the core developers on a machine in the California Bay Area, with bandwidth donated by HotWired. By the end of February, eight core contributors formed the foundation of the original Apache Group:
| Brian Behlendorf |
Roy T. Fielding |
Rob Hartill |
| David Robinson |
Cliff Skolnick |
Randy Terbush |
| Robert S. Thau |
Andrew Wilson |
with additional contributions from
| Eric Hagberg |
Frank Peters |
Nicolas Pioch |
Using NCSA httpd 1.3 as a base, we added all of the published bug fixes and worthwhile enhancements we could find, tested the result on our own servers, and made the first official public release (0.6.2) of the Apache server in April 1995. By coincidence, NCSA restarted their own development during the same period, and Brandon Long and Beth Frank of the NCSA Server Development Team joined the list in March as honorary members so that the two projects could share ideas and fixes.
The early Apache server was a big hit, but we all knew that the codebase needed a general overhaul and redesign. During May-June 1995, while Rob Hartill and the rest of the group focused on implementing new features for 0.7.x (like pre-forked child processes) and supporting the rapidly growing Apache user community, Robert Thau designed a new server architecture (code-named Shambhala) which included a modular structure and API for better extensibility, pool-based memory allocation, and an adaptive pre-forking process model. The group switched to this new server base in July and added the features from 0.7.x, resulting in Apache 0.8.8 (and its brethren) in August.
After extensive beta testing, many ports to obscure platforms, a new set of documentation (by David Robinson), and the addition of many features in the form of our standard modules, Apache 1.0 was released on December 1, 1995.
Less than a year after the group was formed, the Apache server passed NCSA's httpd as the #1 server on the Internet and according to the survey by Netcraft , it retains that position today.
In 1999, members of the Apache Group formed the Apache Software Foundation to provide organizational, legal, and financial support for the Apache HTTP Server. The foundation has placed the software on a solid footing for future development.
|
Getting Involved |
If you just want to send in an occasional suggestion/fix, then you can just use the bug reporting form at < http://httpd.apache.org/bug_report.html >. You can also subscribe to the announcements mailing list ( announce@httpd.apache.org ) which we use to broadcast information about new releases, bugfixes, and upcoming events. There's a lot of information about the development process (much of it in serious need of updating) to be found at < http://httpd.apache.org/dev/
|
| Development |
There is a core group of contributors (informally called the "core") which was formed from the project founders and is augmented from time to time when core members nominate outstanding contributors and the rest of the core members agree. The core group focus is more on "business" issues and limited-circulation things like security problems than on mainstream code development. The term "The Apache Group" technically refers to this core of project contributors.
The Apache Group is a meritocracy -- the more work you have done, the more you are allowed to do. The group founders set the original rules, but they can be changed by vote of the active members. There is a group of people who have logins on our server and access to the CVS repository. Everyone has access to the CVS snapshots. Changes to the code are proposed on the mailing list and usually voted on by active members -- three +1 (yes votes) and no -1 (no votes, or vetoes) are needed to commit a code change during a release cycle; docs are usually committed first and then changed as needed, with conflicts resolved by majority vote.
Our primary method of communication is our mailing list. Approximately 40 messages a day flow over the list, and are typically very conversational in tone. We discuss new features to add, bug fixes, user problems, developments in the web server community, release dates, etc. The actual code development takes place on the developers' local machines, with proposed changes communicated using a patch (output of a unified "diff -u oldfile newfile" command), and committed to the source repository by one of the core developers using remote CVS. Anyone on the mailing list can vote on a particular issue, but we only count those made by active members or people who are known to be experts on that part of the server. Vetoes must be accompanied by a convincing explanation.
New members of the Apache Group are added when a frequent contributor is nominated by one member and unanimously approved by the voting members. In most cases, this "new" member has been actively contributing to the group's work for over six months, so it's usually an easy decision.
The above describes our past and current (as of January 1998) guidelines, which will probably change over time as the membership of the group changes and our development/coordination tools improve.
|
| Why Apache is Free |
Apache exists to provide a robust and commercial-grade reference implementation of the HTTP protocol. It must remain a platform upon which individuals and institutions can build reliable systems, both for experimental purposes and for mission-critical purposes. We believe the tools of online publishing should be in the hands of everyone, and software companies should make their money providing value-added services such as specialized modules and support, amongst other things. We realize that it is often seen as an economic advantage for one company to "own" a market - in the software industry that means to control tightly a particular conduit such that all others must pay. This is typically done by "owning" the protocols through which companies conduct business, at the expense of all those other companies. To the extent that the protocols of the World Wide Web remain "unowned" by a single company, the Web will remain a level playing field for companies large and small. Thus, "ownership" of the protocol must be prevented, and the existence of a robust reference implementation of the protocol, available absolutely for free to all companies, is a tremendously good thing.
Furthermore, Apache is an organic entity; those who benefit from it by using it often contribute back to it by providing feature enhancements, bug fixes, and support for others in public newsgroups. The amount of effort expended by any particular individual is usually fairly light, but the resulting product is made very strong. This kind of community can only happen with freeware -- when someone pays for software, they usually aren't willing to fix its bugs. One can argue, then, that Apache's strength comes from the fact that it's free, and if it were made "not free" it would suffer tremendously, even if that money were spent on a real development team.
We want to see Apache used very widely -- by large companies, small companies, research institutions, schools, individuals, in the intranet environment, everywhere -- even though this may mean that companies who could afford commercial software, and would pay for it without blinking, might get a "free ride" by using Apache. We would even be happy if some commercial software companies completely dropped their own HTTP server development plans and used Apache as a base, with the proper attributions as described in the LICENSE file |
|
| |
|
What Is Samba?
Samba is a suite of Unix/Linux applications that speak the Server Message Block (SMB) protocol. Microsoft Windows operating systems and the OS/2 operating system use SMB to perform client-server networking for file and printer sharing and associated operations. By supporting this protocol, Samba enables computers running Unix to get in on the action, communicating with the same networking protocol as Microsoft Windows and appearing as another Windows system on the network from the perspective of a Windows client. A Samba server offers the following services:
-
Support of Microsoft Domain Controllers
-
Share one or more directory trees
-
Share one or more Distributed filesystem (Dfs) trees
-
Share printers installed on the server among Windows clients on the network
-
Assist clients with network browsing
-
Authenticate clients logging onto a Windows domain
-
Provide or assist with Windows Internet Name Service (WINS) name-server resolution
The Samba suite also includes client tools that allow users on a Unix system to access folders and printers that Windows systems and Samba servers offer on the network.
The latest Samba release supports the migration of Windows NT domain primary and secondary domain controller to linux machines. Samba is now also compliance with the Microsoft Active Directory. see the relaese note |
For complete information on Samba please read the online book at http://samba.mirror.ac.uk/samba/docs/using_samba/toc.html
|
| |
September 24th 2003.
Windows Domain Migration Release
The Samba Team is proud to announce the release of Samba 3.0, a major new release of the award-winning Open Source/Free Software file and print server suite for Microsoft Windows ® clients.
Replacement of Windows NT4 ® Domains
Samba 3.0 contains the first Open Source/Free Software implementation of Windows NT Primary and Backup Domain Controller functionality. Customers can transparently migrate their existing Windows NT domains to Samba 3.0 whilst keeping their existing user and group account databases. This enables significant cost of ownership savings over a Windows NT4 domain as a Samba 3.0 Domain Controller does not require client access licenses. Existing Windows tools can be used to manage a Samba PDC, allowing customer Windows expertise to be leveraged in a domain migration. A choice of LDAP back-ends allows integration with an existing customer directory service.
Single Sign-on with Active Directory ® Integration
Samba 3.0 seamlessly integrates into a Microsoft Active Directory domain in both native and mixed mode. Samba 3.0 provides single sign-on for UNIX ® / Linux ® clients in an Active Directory environment, allowing both servers and clients to transparently use Active Directory as an authentication and account source. Domain trust relationships are fully supported, allowing Samba 3.0 Controlled Domains to integrate easily into any Active Directory environment.
Complete Integration with Windows Security
Samba 3.0 fully implements Kerberos 5 authentication, SMB signing for tamper-proof file serving sessions, and SCHANNEL security for secure remote procedure calls. Samba 3.0 works "out of the box" with the improved security settings of Windows 2003 Domain Controllers.
A Global File and Print Server
As Samba is a global project, internationalization support is an important feature. Samba 3.0 now implements UNICODE character sets on the wire, allowing clients using any character set to connect to a single file server and store names in their native character sets.
David de Leeuw. Head, Medical Computing Unit
Ben Gurion University of the Negev, Israel wrote :
"With the release of Samba 3 we are able for the first time to store our files on the computer servers in any language we want. Filenames in English, Hebrew, Arabic, Russian, and scores of other languages, used by our staff and students, mix without problems thanks to the great new UNICODE support of Samba."
Scalable Printing
Samba 3.0 has been tested in production supporting thousands of print queues with tens of thousands of simultaneous print jobs, providing the most scalable Windows printing solution on the market. Samba 3.0 fully supports the Windows "point-and-print" driver download feature, allowing Samba 3.0 to provide a transparent Windows printing experience.
Comprehensive Documentation
Samba 3.0 ships with the second edition of "Using Samba" by Jay Ts, Robert Eckstein, and David Collier-Brown (O'Reilly & Associates ®). Many thanks to the authors and publisher for making "Using Samba" available under the GNU Free Documentation License.
In addition, the Samba HOWTO documentation collection has been updated and improved by John H. Terpstra, Jelmer R. Vernooij and others. As well being freely available in the Samba 3.0 release it will be released in a forthcoming book, "The Official Samba-3 HOWTO and Reference Guide", to be published by Prentice Hall ®.
Award Winning Linux/UNIX and Windows Integration
Samba has won many awards for providing Windows and Linux/UNIX connectivity. Last year, Samba was awarded the Innovation in Infrastructure prize in the "Enterprise Software" category by eWeek and PC Magazine, beating out such competitors as the Java 2 Platform.
David A. Licosati, Vice President, InoStor Corporation said :
"Samba 3.0 goes beyond expectations. The team's work allows us to penetrate markets and open up new areas of deployments heretofore unobtainable."
Samba is the leading choice for Windows connectivity
Samba 3.0 is fully portable, POSIX compliant software that runs on a variety of UNIX and UNIX-like systems including AIX ®, DG/UX ®, FreeBSD, HPUX®, IRIX ®, Linux ®, Mac OS X ® and Solaris ®. Samba is shipped as standard on all versions of Linux, and most of the major vendors versions of UNIX as a fully supported part of the operating system.
Getting Samba 3.0
Samba 3.0 is available now from the Samba Web site and all worldwide mirrors.
www.samba.org
About the Samba Team
The Samba Team is a worldwide group of computer professionals working together via the Internet to produce the highest quality Open Source/Free Software Windows (SMB/CIFS) server software.
|
| |
|
The Xen virtual machine monitor
Modern computers are sufficiently powerful to use virtualization to present the illusion of many smaller virtual machines (VMs), each running a separate operating system instance.
Xen virtual machine monitor is a high-performance hypervisor for hosting multiple commodity operating systems on a single x86-based server. This forms the core of each Xenoserver node, providing the resource management, accounting and auditing that we require. Xen finds numerous applications outside the Xenoserver project. These inclue server consolidation and secure computing platforms
Successful partitioning of a machine to support the concurrent execution of multiple operating systems poses several challenges. Firstly, virtual machines must be isolated from one another: it is not acceptable for the execution of one to adversely affect the performance of another. This is particularly true when virtual machines are owned by mutually untrusting users. Secondly, it is necessary to support a variety of different operating systems to accommodate the heterogeneity of popular applications. Thirdly, the performance overhead introduced by virtualization should be small.
Xen is a virtual machine monitor for x86 that supports execution of multiple guest operating systems with unprecedented levels of performance and resource isolation. Xen is Open Source software, released under the terms of the GNU General Public License. We have a fully functional port of Linux 2.4 running over Xen, and regularly use it for running demanding applications like MySQL, Apache and PostgreSQL. Any Linux distribution should run unmodified over the ported OS.
With assistance from Microsoft Research, we have a port of Windows XP to Xen nearly complete, and are planning a FreeBSD 4.8 port in the near future (volunteers welcome!).
Our paper Xen and the Art of Virtualization at SOSP 2003 provides an up-to-date overview and performance evaluation of Xen.
Xen is a key component of the XenoServers project, which aims to build an "Open Infrastructure for Global Distributed Computing". The project publications page provides further information and the rationale for different aspects of the design of Xen.
Visit the project download page for the XenDemoCD, or the pre-built source tree. Both are released under the GNU GPL.
|
Exim |
Exim is a message transfer agent ( MTA ) developed at the University of Cambridge for use on Unix systems connected to the Internet. It is freely available under the terms of the GNU General Public Licence . In style it is similar to Smail 3 , but its facilities are more general. There is a great deal of flexibility in the way mail can be routed, and there are extensive facilities for checking incoming mail. Exim can be installed in place of sendmail, although the configuration of exim is quite different to that of sendmail.
Email is the most widely used application on the Internet. Exim is rapidly becoming one of the most widely used mail servers, handling mail for tens of millions of users daily.
- Exim is free software.
- Exim is easy to configure. Its configuration files are easy to understand and edit.
- Exim is scalable. It runs on single-user desktop systems as well as on ISP servers handling millions of users.
- Exim is the default server already installed on many Linux systems, and it's available for countless versions of UNIX.
- Exim is fast.
- Exim is reliable. It is designed not to lose messages even if your server machine crashes.
- Exim is flexible. It supports lookups from LDAP servers, SQL databases, and other data sources, letting you automate maintenance and configuration. It can work with other tools, e.g. for virus-checking.
- Deploy Exim as your SMTP email server throughout your organization.
- Configure a reliable mail service to meet the specific needs of your site.
- Manage your email system's daily operations, monitor its performance, interpret logs, and troubleshoot mail problems.
- Filter messages: save messages to files or divert them to other addresses, or check them for spam or viruses and delete them if they do.
- Tune your server to give optimal performance in your environment.
- Handle multiple domains for large organizations and "virtual" domains for ISP-type environments.
- Simplify your email management.
- Secure your email system to prevent unauthorized use and maintain the confidentiality of messages.
|
| Homepage: www.exim.org |
| Current Version: 4.24 |
| Documentations: A comprehensive docs for EXIM |
| Download: ftp sites |
| |
|
| |
|
|
