Previous Topic: Web Server AppliancesNext Topic: WEBx4 - Scalable Web Server Appliance


WEB5, WEB64 - Web Server Appliances

Simple Web Server Appliance

At a Glance

Catalog

System

Category

Web Servers

User volumes

yes

Min. memory

160 MB

OS

Linux

Constraints

no

Questions/Comments

Ask Forum

Functional Overview

Important! WEB4 is not available in CA 3Tera AppLogic 2.8+; use WEB5 or WEB64 instead.

WEB is a web server appliance based on the Apache open source web server software (see http://httpd.apache.org).

WEB serves static web content and executes scripts from a user-configurable read-only content volume. The paths to the documents and scripts are configurable, so that the same volume can be shared between multiple web servers and/or other appliances serving different content.

WEB has three generic output terminals intended for accessing external services from scripts on the content volume. The db terminal is for accessing a MySQL database; the fs terminal is for accessing shared file storage (using NFS); and the aux terminal is for any auxiliary access (for example, sending e-mail messages to a SMTP server).

The log terminal can be used to connect WEB to a shared file system on which WEB can store its logs.

The configuration of the web server is provided through properties. The properties are designed to cover the most uses in an easy-to-configure way and in most cases only a few need to be set to non-default values. Advanced configurations can be achieved through include files in the Apache configuration format, coming from the content volume. Access and options to content and script files can be further specialized through .htaccess files in the content directories.

If the features provided by the WEB appliance do not meet your needs, contact our Technical Support to discuss the possible options. We may be able to extend the catalog by providing appliances that cover your needs.

Name

Latest Version

OS

Apache

PHP

Python

Perl

MySQL client libs

Notes

WEB5

2.0.2-1

CentOS 5.5

2.2.3

5.1.6

2.4.3

5.8.8

5.0.22

 

WEB64

2.0.2-1

CentOS 5.5 (64 bit)

2.2.3

5.1.6

2.4.3

5.8.8

5.0.22

 

Boundary

Resources

Resource

Minimum

Maximum

Default

CPU

0.1

16

0.3

Memory

160MB

32 GB

512 MB

Bandwidth

1 Mbps

2 Gbps

250 Mbps

Terminals

Name

Dir

Protocol

Description

in

in

HTTP

Serves HTTP requests coming from web clients. Serves the HTTP/1.1 and 1.0 protocols.

db

out

MYSQL

Access to a MySQL server. Usage is defined by whatever scripts reside on the content volume (if any). This terminal may be left unconnected if it is not used.

fs

out

NFS

Access to a network file system for shared file storage, providing read/write file access over NFS. Usage is defined by whatever scripts reside on the content volume (if any). Software on the content volume 'sees' the mounted remote file system as /mnt/fs in the appliance's filesystem space. This terminal may be left unconnected if it is not used. The connected server must have a read-write share named /mnt/data.

log

out

CIFS

Access to a CIFS-based network file system for storing access and error logs. This terminal may be left unconnected if it is not used. The connected server must allow anonymous logins and have a read-write share named share.

aux

out

Any

Access to any auxiliary service (for example, a SMTP server for sending outgoing e-mail). Usage is defined by whatever scripts reside on the content volume (if any).
This terminal may be left unconnected if it is not used.

net

out

Any

Gateway output for subnet access.
This terminal may be left unconnected if it is not used.

mon

out

CCE

Sends performance and resource usage statistics.
This terminal may be left unconnected if it is not used.

The default interface is enabled. The default interface is used by the appliance to report to CA 3Tera AppLogic that it has booted successfully. It can also be used to log in over secure shell to the appliance from the CA 3Tera AppLogic controller, primarily for diagnostic and troubleshooting purposes.

User Volumes

Volume

Description

content

Read-only, shareable volume providing the web content (documents, media and scripts) to be served by WEB.

The volume may provide static and/or dynamic content with an optional configurable directory dedicated for scripts. Script execution from any directory can also be configured using a file name pattern.

In addition to content, the document directory (configured through the docs_dir property) on the content volume may also hold the following optional configuration files, all in the standard Apache configuration format (see http://httpd.apache.org/docs/2.2):

Properties

Property name

Type

Description

host_name

String

Host name of the website. WEB uses this name to display in automatically generated pages, as well as for constructing absolute URLs, for example, in server-generated redirects (for example, as may be set up in a custom config file installed on the content volume). Although explicit redirects are rarely configured, a request for a directory without the trailing '/' causes a re-direct to be issued to the client, with the '/' appended; this redirect will use the value of host_name if it is set.
Setting this property correctly is recommended if WEB is expected to be accessed by older clients that do not send a Host: header with their HTTP requests.
If this property is set to an empty string, the host name used in the client's request is used.
Default: (empty)

admin_email

String

E-mail address for the server administrator. WEB uses this name to display it in automatically generated pages.
Default: root@localhost

content_on_fs

String

Specifies whether the content is relative to the file system at the fs terminal or is on the content volume. Allowed values are on and off. If set to on, all content is relative to the file system at the fs terminal. If set to off, the content is on the content volume.
Default: off

docs_dir

String

Root directory on the content volume where the documents to be served are located. For example, it may be /mydocs. This property is convenient to use when more than one WEB server share the content volume and each server needs its own documents. If docs_dir is set to the empty string, the root directory of the content volume is used.
Note: The directory must be pre-existing on the content volume.
Default: (empty)

docs_loc

String

An optional location within the client-visible namespace where the content should appear ("client-visible namespace" is the path portion of a URL, or what appears to the right of the host name in a URL, including the leading /). If set to a non-empty value, this becomes the namespace root, as seen by the client, where the document root directory appears. For example, if docs_loc is set to subspace/samples, an HTTP request for /subspace/samples/file1.html will serve file1.html from the document root directory. A request for a location outside /subspace/samples will return an error, except if it is a request for a script in the scripts directory (see scripts_loc).
This property is useful when WEB serves a subspace of a website. Do not append a trailing slash to this value.
Default: (empty)

scripts_dir

String

Root directory on the content volume where CGI scripts are located. For example, it may be /scripts. This should be set to a non-empty value, referring to a directory on the content volume that contains only executable scripts (don't set it to "/").
Note: The directory must be pre-existing on the content volume.
Default: (empty)

scripts_loc

String

The location in the web space where the scripts directory specified by scripts_dir should be visible. This must be set to a non-empty string to enable the use of a dedicated scripts directory. A typical value may be /cgi-bin. Do not append a trailing slash to this value.
Default: (empty)

logs_enabled

String

Controls whether WEB will send its logs out the log terminal. Allowed values are on and off. If set to on, the log terminal must be connected. If this is set to off, no access log is used at all and the error log is written to a file on the root filesystem of the WEB instance, rotated weekly, with 4 weeks of back logs kept (/var/log/httpd/error_log*). Default: off

logs_base_dir

String

Directory where WEB's logs are stored. This property has no effect if logs_enabled is set to 'off'. Default: /

access_log_filename

String

Filename for the access log, relative to the file system accessible on the log terminal. For example, access_log. The name may include directory names, for example, /srv1_logs/access_log or /logs/srv1_access_log. If empty, access log is not created. If the directories do not exist, they will be created. This proper has no effect if logs_enabled is set to off. Default: (empty)

error_log_filename

String

Filename for the error log, relative to the file system accessible on the log terminal. The name may include directory names. For examples, see the access_log_filename. If this is set to an empty value or if logs_enabled is 'off', the error log is written to a file on the root filesystem of the WEB instance itself. This proper has no effect if logs_enabled is set to 'off'. Default: (empty)

error_log_level

String

Severity level of messages to be written to the error log. Allowed values are debug, info, notice, warn, error, crit, alert and emerg. debug writes most messages, emerg writes only emergency messages. Default: warn

timezone

String

Specifies the time zone where the appliance is located. If this property is empty, the timezone is not modified and left as-is. A list of supported time zones is available here. Default: empty

Important! All enumerated string properties are not case sensitive (lowercase). All other string properties are case sensitive.

Advanced Properties

These are additional properties that should typically not need to be configured. They can be used to tune up WEB in non-standard circumstances.

Property name

Type

Description

cgi_ext

String

Defines the file name suffixes for CGI scripts as a space-separated list. This is used to specify which files to treat as executable CGI scripts (in any directory) and can be used as an alternative to specifying a common scripts directory - see the scripts_dir and scripts_loc properties. Default: .cgi

shared_perl_ext

String

Defines the file name suffixes for in-process Perl scripts as a space-separated list. This is used to specify which files to treat as Perl scripts to be run with mod_perl. Any extension that matches one already specified in cgi_ext overrides the use of CGI for that extension and configures it to be run by mod_perl instead. The in-process Perl module is configured to run scripts with the specified extensions in CGI compatibility mode - most Perl scripts designed to be run as CGI processes should work if set up as in-process scripts too. Note: It is important to check your scripts for proper initialization of all file-scope variables, for example, with use strict; use warnings because all scripts run by mod_perl execute without re-starting the Perl interpreter. If unsure whether your scripts will work with mod_perl, review the mod_perl documentation for more information: http://perl.apache.org/docs/index.html.
Default: (empty) (that is, don't use mod_perl)

index_files

String

Ordered, space-separated list of files to use as a directory index page in case the client requests a URL that refers to a directory name.
Default: index.html index.html.var

use_htaccess

String

Specifies whether to enable the use of .htaccess files for the entire document tree. This is disabled by default and should be used only if you have a content directory structure that requires fine-grain control of server options, but is too complicated to configure using a set of sections in a common config file, or if you have a pre-configured content volume that already uses .htaccess and want to avoid the hassle of re-arranging it. If config options are needed only for the document root itself, put your settings in the document root directory in the .htconf file instead - they will be applied exactly the same way as for .htacces, except the file is read once at boot time. Default: off

max_connections

Integer

Maximum number of concurrent active connections that WEB can handle. If this limit is reached, additional connection requests are queued (up to a limit of 511) and processed as currently active connections get closed. This value should be raised only if WEB is expected to serve a large number of requests that need access to a slow external source of data (for example, lengthy database queries). The actual number of concurrent connections may be limited below the value set for this property, if there is not enough system memory. See the Memory Usage section. The max_connections value cannot be set to more than 256.
Default: 128

persistent_connections

String

Controls whether WEB allows clients to request more than one document on the same connection. Allowed values are on, off. You may need to disable the persistent connections only if you have problems with clients that don't support HTTP/1.1 properly but don't fall back to HTTP/1.0. Default: on

idle_timeout_sec

Integer

Timeout, in seconds, for keeping a client connection open if there is no request or response going through. This property is used only if persistent_connections is on. Keeping this timeout short helps drop forgotten connections quickly. Default: 15

data_timeout_sec

Integer

Timeout, in seconds, for receiving or sending more data if a data transfer has started but is not completed. Having this timeout allows WEB to drop connections that got forgotten, while still allowing delays during the transfer. Default: 300

default_charset

String

Default character set to report for returned documents of type text/html or text/plain. The property should be set either to the name of a character set or to off (to disable sending of a charset header in HTTP responses). Note: For some browsers setting this property can override the character set value provided by the author of the served HTML documents and is therefore recommended only if there are documents that do not contain a valid character set specification and it is known in advance that all documents served by this instance of WEB are in the same character set. Typical example values may be iso-8859-1 or utf-8. Default: Off
Note: To cover for special cases, including old CGI scripts that do not generate a proper content-type meta tag, per-directory setting of the default charset is possible using custom configuration files stored on the content volume.

info_level

String

Controls how much information WEB discloses about itself to web clients (in HTTP responses and in automatically generated pages). Allowed values are full (most info), os, minor, major, prod (least info). As a security measure, it is recommended that you disclose the minimum information. Default prod

server_signature

String

Controls whether WEB appends a server signature line at the bottom of all generated pages (for example, on error pages). Allowed values are on, off. The amount of information WEB includes in the signature is controlled by info_level. Default off (no signatures).

env

String

Used to pass settings to WEB as name=value pairs. Its up to the user to parse and use those values, they are not set in the environment. Default: (empty)

web_console

String

Controls whether the appliance may be accessed using the “Login (Web)” button on the toolbar of the grid controller “Application” tab. Allowed values are “on” and “off”. If set to “on” and the application is running and the application is selected in the grid controller application list and this appliance is the default console for the application, the “login (web)” button in the toolbar will launch a new browser window showing the web site hosted on this appliance. Default: “off”

Important! All enumerated string properties are not case sensitive (lowercase). All other string properties are case sensitive.

Custom Counters

The WEB appliance reports the following custom counters through the mon terminal.

The following counters belong to the Apache counter group:

Counter name

Description

Total hits

Total number of hits

Total bytes

Total number of bytes

Active requests

Number of active requests

Idle servers

Number of idle servers

Error Messages

The following messages may appear in either the appliance log file or the system log of the grid controller when the appliance fails to start:

Logs are enabled but the log terminal is not connected.

Memory Usage

WEB configures itself automatically to run with a wide range of available memory, to fit applications of different size and load. Despite this, please note that the configuration calculation cannot predict the memory usage of dynamic-content scripts that may be installed on the WEB's content volume and a misbehaving script can cause the server to malfunction by over-committing memory and causing the OS to kill processes.

By default, WEB configures the maximum number of active connections assuming:

For example, in the 'sandbox' configuration with 32M, the max number of active connections will be set to 8.

The maximum number of connections can be limited below the automatically computed value using the max_connections property. Remember that if max_connections is above the limit imposed by the available system memory, it is trimmed without warning.

In addition, the PHP pre-processor's allocation limit is set to 1/2 the memory available for scripts, as computed according to the above rules, that is, the PHP is configured to limit the memory for a running script to

(system_memory - 16MB - max_connections * 1MB) / 2 

Where the max_connections value is the smaller of the max_connections property and the limit imposed by the available memory (computed assuming 2MB per connection, as described above). If the max_connections property is left at its default value, this will yield the following value for the PHP memory limit:

(system_memory - 16MB) / 4 

Note: The "1/2 of available memory per script" rule used is somewhat optimistic and is based on the assumption that either not all active connections will use a hungry PHP script that actually hits the limit, or that the scripts do not actually use all the memory that they allocate.

TIP: If a memory-heavy application starts misbehaving under load (drops connections), and increasing the available memory is not an option, try setting the max_connections property to a lower value. This will reduce the possible number of script instances that run at the same time, giving each instance more memory to run in.

Setting Up The Content, Shared File Storage

This section provides useful information for configuring scripts that serve dynamic content.

Fixed Directory Names

On starting the HTTP server, the following directories and files are available within the filesystem space of the WEB instance. Note that using absolute directory names outside of these locations in any script or configuration file is not recommended.

/var/www/html - web root, visible as '/' to the client. This refers to a location on the content volume and is read-only. Note: If the 'docs_loc' property is set, then /var/www/html itself will have no data files in it. Appending the value of docs_loc will produce the name of a valid symbolic link that refers to the document root. This directory name and the /var/www/cgi-bin name and any of their sub-directories can be used in Apache configuration files to set up additional per-directory settings. This avoids the need for such configuration files to be aware of the particular setting for the docs_dir and scripts_dir properties.

/var/www/cgi-bin - symbolic link to the scripts root, if set up using the scripts_dir property.

/mnt/fs - root of the shared read/write file storage provided by a NFS server connected to the 'fs' terminal. If one is not connected, /mnt/fs will be empty.

Fixed Web Space Locations

The /icons/ path is aliased to a directory containing stock icons for server-generated directory listings. Therefore, a directory named icons in the content volume will not be visible.

Access Control

The HTTP server runs as user 48, group 48. CGI scripts run in the same context.

Files on the content volume should have read permission for everyone, to be eligible for serving through HTTP. Executable scripts should have read and execute permissions for everyone.

Although the Apache server has other means to control access to files, one may also remove the read permission for everyone from files or directories that should not be made accessible through HTTP. Do leave the x bit set on for directories for which a listing should not be accessible, but contain files or sub-directories that are accessible.

Sending E-mail

The sendmail system is not configured on WEB. Do not use it for sending e-mail from this appliance. To provide access to an external SMTP server, connect the aux terminal to an appliance which provides this functionality or to an OUT gateway directed to a server outside of the application. If using Perl-based scripts, the Mail::Mailer module can be used for sending e-mail, if it is configured to use the smtp mailer. In all cases, your SMTP mailer should be set up to use 'aux' as the hostname of the SMTP server, for example, if using Mail::Mailer :

$mailer = new Mail::Mailer 'smtp', (Server => 'aux');
$mailer->open(\%headers); #... etc.

Installing Additional PHP/Perl Modules On The Content Volume

Install PHP Modules

WEB comes with all PHP packages available in the official CentOS mirror. If you are using the fs share instead of a read-only content volume, you can install additional PHP modules without branching the appliance.

To install PHP modules

  1. Install all required software dependencies. If you are installing from an RPM package, check for unsatisfied dependencies with the --test option. For example:
    rpm --test -Uv php-mhash-5.1.6-5.el5.i386.rpm
    

    If you are using RPM packages for the dependencies, check that they do not have unsatisfied dependencies of their own. For example:

    rpm --test -Uv libmhash-0.9.1-1.2.el5.rf.i386.rpm
    

    Then install all required RPM's on the fs share. For example:

    rpm --root=/mnt/fs/php -Uv --nodeps libmhash-0.9.1-1.2.el5.rf.i386.rpm
    

    If you are not installing the PHP module from an RPM, help ensure that it is compatible with the version of PHP used in WEB and that it does not require any additional libs (ldd /path/to/php/module.so). If you have unsatisfied dependencies, install the needed software on the fs share.

  2. Install the PHP module on the fs share. For example:
    rpm --root=/mnt/fs/php -Uv php-mhash-5.1.6-5.el5.i386.rpm
    

    This installs the RPM under /mnt/fs/php.

  3. Create a .rc.local script that updates the PHP configuration on appliance boot. Because the PHP module is installed on the fs share, the PHP installed on the appliance is not aware of the extra software. To make PHP aware of the installed appliance, create an .rc.local script which creates a custom PHP config file. The .rc.local script is executed every time the appliance starts.
    The script looks as follows:
    #!/bin/bash
    
    # die on all errors
    set -e
    
    # Add configuration to the main php conf dir. Path to extensions must be changed to be relative to /usr/lib/php/modules/
    sed  's/extension=\(.*\)$/extension=..\/..\/..\/..\/mnt\/fs\/php\/usr\/lib\/php\/modules\/\1/g' /mnt/fs/php/etc/php.d/*ini > /etc/php.d/custom-php.ini
    
    # If we installed any dependent libs on the =fs= share, we need to tell ldconfig to load them
    # You can skip this if you did not install any dependent libs on the =fs= share
    echo /mnt/fs/php/usr/lib > /etc/ld.so.conf.d/custom-libs.conf
    ldconfig
    
    # Restart apache and check status
    /etc/init.d/httpd restart
    sleep 1
    

/etc/init.d/httpd status

Install Perl Modules

CA 3Tera AppLogic lets you install Perl modules.

To install Perl modules

  1. Install all the required software.

    Note: For more information about how to install software dependencies on fs share, see the PHP section. If you install any libs, inform ldconfig to load them. Use the following .rc.local file:

    #!/bin/bash
    
    # die on all errors
    set -e
    
    # If we installed any dependent libs on the =fs= share, we need to tell ldconfig to load them
    # You can skip this id you did not install any dependent libs on the =fs= share
    echo /mnt/fs/php/usr/lib > /etc/ld.so.conf.d/custom-libs.conf
    ldconfig
    
  2. Install the Perl modules.

    Note: The WEB appliance does not come with build tools, so you cannot build Perl modules on the appliance. Either use prepackaged modules (RPM RPModules) or build the Perl modules in a separate build environment (use LINUX5) and package them. You can use cpan2rpm (http://sourceforge.net/projects/cpan2rpm/) to create an RPM from a CPAN module.

  3. Add the installation path to your Perl include path.

    Note: To make Perl programs use the installed modules, provide where install location. Set @INC to include the install directory on the fs share, or set this path to the PERL5LIB environment variable which is added to @INC.

    For Perl running as CGI, add the following to a.htconf file on your fs share to add the install path to @INC:

    SetEnv PERL5LIB  /mnt/fs/perl_mods/usr/lib/perl5/vendor_perl/5.8.8/ 
    

    For Perl running as mod_perl, add the following to .htconf:

PerlSwitches -I/mnt/fs/perl_mods/usr/lib/perl5/vendor_perl/5.8.8/

Typical Usage

Static web site

Static web site

2-tier application with database

2-tier application with database

2-tier application with database and log

2-tier application with database and log

2-tier application with shared file system and e-mail gateway

2-tier application with shared file system and e-mail gateway

Scalable 2-tier application

Scalable 2-tier application

(see also the Sample SugarCRM application)

Additional Information

Known Limitations

Be aware of the following:

For further assistance and suggestions, contact CA Technical Support.

Open Source and Third Party Software Used on the Appliance

The following open source 3rd party software is used in addition to that software found on the appliance base class (LUX5 is the base class of WEB5 and LUX64 is the base class of WEB64).

Software

Version

Modified

License

Notes

alsa-lib

1.0.17-1

No

LGPLv2.1

N/A

apr

1.2.7-11

No

Apache License v2.0

N/A

apr-util

1.2.7-11

No

Apache License v2.0

N/A

aspell

0.60.3-7.1

No

LGPLv2.1

N/A

aspell-en

6.0-2.1

No

ISC

N/A

atk

1.12.2-1.fc6

No

LGPLv2.0

N/A

audiofile

0.2.6-5

No

LGPLv2.0

N/A

audit-libs-python

1.7.17-3

No

GPLv2

N/A

avahi

0.6.16-9.el5_5

No

LGPLv2.1

N/A

avahi-glib

0.6.16-9.el5_5

No

LGPLv2.1

N/A

bind-libs

9.3.6-4.P1.el5_4.2

No

ISC

N/A

bind-utils

9.3.6-4.P1.el5_4.2

No

ISC

N/A

bitstream-vera-fonts

1.10-7

No

GPLv2

N/A

cairo

1.2.4-5

No

LGPLv2.1/MPL

N/A

chkfontpath

1.10.1-1.1

No

GPLv2

N/A

cryptsetup-luks

1.0.3-5

No

GPLv2

N/A

cups-libs

1.3.7-18.el5_5.7

No

GPLv2

N/A

curl

7.15.5-9

No

MIT

N/A

cyrus-sasl

2.1.22-5.el5_5.3

No

BSD

N/A

dbus

1.1.2-14

No

AFLv2.1

N/A

dbus-glib

0.73-10.el5_5

No

AFLv2.1

N/A

dbus-libs

1.1.2-14

No

AFLv2.1

N/A

dbus-python

0.70-9.el5_4

No

AFLv2.1

N/A

distcache

1.4.5-14.1

No

LGPLv2.1

N/A

dmidecode

2.10-3

No

GPLv2

N/A

esound

0.2.36-3

No

GPLv2

N/A

fontconfig

2.4.1-7

No

ISC

N/A

freetype

2.2.1-28.el5_5

No

FTL

N/A

gamin

0.1.7-8

No

LGPLv2.1

N/A

GConf2

2.14.0-9

No

LGPLv2.1

N/A

gd

2.0.33-9.4.el5_4.2

No

GD

N/A

ghostscript

8.15.2-9.12.el5_5

No

GPLv2

N/A

ghostscript-fonts

5.50-13.1.1

No

GPLv2

N/A

gmp

4.1.4-10

No

LGPLv2.1

N/A

gnome-keyring

0.6.0-1.fc6

No

GPLv2

N/A

gnome-mime-data

2.4.2-3.1

No

GPLv2

N/A

gnome-mount

0.5-3

No

GPLv2

N/A

gnome-vfs2

2.16.2-6.el5_5.1

No

LGPLv2.0

N/A

gnutls

1.4.1-3.el5_4.8

No

LGPLv2.1

N/A

gtk2

2.10.4-20

No

LGPLv2.0

N/A

hal

0.5.8.1-59

No

AFLv2.1

N/A

hesiod

3.1.0-8

No

ISC

N/A

hicolor-icon-theme

0.9-2.1

No

GPLv2

N/A

httpd

2.2.17-1

No

Apache License v2.0

N/A

hwdata

0.213.18-1

No

GPLv2

N/A

kbd

1.12-21

No

GPLv2

N/A

kernel-headers

2.6.18-194.17.4

No

GPLv2

N/A

lcms

1.18-0.1.beta1.el5_3.2

No

MIT

N/A

libart_lgpl

2.3.17-4

No

LGPLv2.0

N/A

libbonobo

2.16.0-1.1.el5_5.1

No

LGPLv2.1

N/A

libbonoboui

2.16.0-1.fc6

No

LGPLv2.1

N/A

libc-client

2004g-2.2.1

No

Apache License v2.0

N/A

libcroco

0.6.1-2.1

No

LGPLv2.0

N/A

libdaemon

0.10-5

No

LGPLv2.1

N/A

libfontenc

1.0.2-2.2

No

MIT

N/A

libFS

1.0.0-3.1

No

ISC

N/A

libgcrypt

1.4.4-5

No

LGPLv2.1

N/A

libglade2

2.6.0-2

No

LGPLv2.0

N/A

libgnome

2.16.0-6

No

LGPLv2.0

N/A

libgnomecanvas

2.14.0-4.1

No

LGPLv2.0

N/A

libgnomeui

2.16.0-5

No

LGPLv2.0

N/A

libgpg-error

1.4-2

No

LGPLv2.1

N/A

libgsf

1.14.1-6.1

No

LGPLv2.1

N/A

libICE

1.0.1-2.1

No

MIT

N/A

libIDL

0.8.7-1.fc6

No

LGPLv2.0

N/A

libidn

0.6.5-1.1

No

LGPLv2.1

N/A

libjpeg

6b-37

No

distributable

N/A

libnotify

0.4.2-6

No

LGPLv2.1

N/A

libpng

1.2.10-7.1.el5_5.3

No

zlib

N/A

librsvg2

2.16.1-1

No

LGPLv2.0

N/A

libSM

1.0.1-3.1

No

MIT

N/A

libtiff

3.8.2-7.el5_5.5

No

ISC

N/A

libusb

0.1.12-5.1

No

LGPLv2.0

N/A

libutempter

1.1.4-4

No

LGPLv2.1

N/A

libwmf

0.2.8.4-10.2

No

GPLv2

N/A

libwnck

2.16.0-4.fc6

No

LGPLv2.0

N/A

libX11

1.0.3-11

No

MIT

N/A

libXau

1.0.1-3.1

No

MIT

N/A

libXcursor

1.1.7-1.1

No

ISC

N/A

libXdmcp

1.0.1-2.1

No

MIT

N/A

libXext

1.0.1-2.1

No

MIT

N/A

libXfixes

4.0.1-2.1

No

ISC

N/A

libXfont

1.2.2-1.0.3.el5_1

No

MIT-X11

N/A

libXft

2.1.10-1.1

No

ISC

N/A4

libXi

1.0.1-4.el5_4

No

MIT

N/A

libXinerama

1.0.1-2.1

No

MIT

N/A

libxml2-python

2.6.26-2.1.2.8.el5_5.1

No

MIT

N/A

libXpm

3.5.5-3

No

MIT

N/A

libXrandr

1.1.1-3.3

No

MIT

N/A

libXrender

0.9.1-3.1

No

ISC

N/A

libXres

1.0.1-3.1

No

MIT

N/A

libxslt

1.1.17-2.el5_2.2

No

MIT

N/A

libXt

1.0.2-3.2

No

ISC

N/A

lm_sensors

2.10.7-9

No

GPLv2

WEB64 only

mailcap

2.1.23-1.fc6

No

ISC

N/A4

make

3.81-3

No

GPLv2

N/A

mod_auth_mysql

3.0.0-3.2.el5_3

No

Apache Group

N/A

mod_perl

2.0.4-12

No

Apache License v2.0

N/A

mod_rpaf

0.5

Yes

Apache Group

N/A

mod_ssl

2.2.17-1

No

Apache License v2.0

N/A

MySQL? -client-community

5.1.51

No

GPLv2

N/A

MySQL? -shared-compat

5.1.51

No

GPLv2

N/A

net-snmp

5.3.2.2

No

BSD

WEB64 only

net-snmp-libs

5.3.2.2

No

BSD

WEB64 only

notification-daemon

0.3.5-9

No

GPLv2

N/A

ntsysv

1.3.30.2-2

No

GPLv2

N/A

ORBit2

2.14.3-5

No

LGPLv2

N/A

pango

1.14.9-8

No

LGPLv2.0

N/A

pciutils

2.2.3-8.el5_4

No

GPLv2

N/A

perl

5.12.2-1

No

Artistic

WEB64 only

perl-AppConfig

1.65-1

No

Artistic

N/A

perl-BSD-Resource

1.28-1

No

Artistic

N/A

perl-DBD-MySQL

3.0007-2

No

Artistic

N/A

perl-DBD-Pg

1.49-2

No

Artistic

N/A

perl-DBD-SQLite

1.29-1

No

Artistic

N/A

perl-DBI

1.615-1

No

Artistic

N/A

perl-DBIx-Simple

1.32-1

No

Artistic

N/A

perl-GD

2.35-1

No

Artistic

N/A

perl-Mailtools

1.77-1

No

Artistic

WEB64 only

perl-Pod-POM

0.17-1.2

No

Artistic

N/A

perl-String-CRC32

1.4-2

No

Public Domain

N/A

perl-Template-Toolkit

2.15-1

No

Artistic

N/A

perl-Text-Autoformat

1.13-1.2

No

Artistic

N/A

perl-Text-Reform

1.11-1.2

No

Artistic

N/A

perl-TimeDate

1.16-5

No

Artistic

WEB64 only

perl-Unicode-String

2.09-1

No

Artistic

N/A

perl-Digest-SHA1

2.11-1.2.1

No

Artistic

WEB5 only

php53

5.3.3-4

No

PHP v3.01

N/A

php53-cli

5.3.3-4

No

PHP v3.01

N/A

php53-bcmath

5.3.3-4

No

PHP v3.01

WEB64 only

php53-common

5.3.3-4

No

PHP v3.01

N/A

php53-dba

5.3.3-4

No

PHP v3.01

WEB64 only

php53-gd

5.3.3-4

No

PHP v3.01

N/A

php53-imap

5.3.3-4

No

PHP v3.01

N/A

php53-ldap

5.3.3-4

No

PHP v3.01

WEB64 only

php53-mysql

5.3.3-4

No

PHP v3.01

N/A

php53-mssql

5.3.3-4

No

PHP v3.01

WEB5 only

php53-odbc

5.3.3-4

No

PHP v3.01

WEB64 only

php53-pdo

5.3.3-4

No

PHP v3.01

N/A

php53-pear

5.3.3-4

No

PHP v3.0

N/A

php53-pgsql

5.3.3-4

No

PHP v3.01

N/A

php53-snmp

5.3.3-4

No

PHP v3.01

WEB64 only

php53-soap

5.3.3-4

No

PHP v3.01

WEB64 only

php53-xml

5.3.3-4

No

PHP v3.01

WEB64 only

php53-xmlrpc

5.3.3-4

No

PHP v3.01

WEB64 only

php53-mbstring

5.3.3-4

No

PHP v3.01

WEB5, WEB64

pkgconfig

0.21-2

No

GPLv2

WEB5, WEB64

pm-utils

0.19

No

GPLv2

WEB5, WEB64

policycoreutils

1.33.12-14.8

No

GPLv2

WEB5, WEB64

postgresql90-libs

9.0.1-1PGDG

No

BSD

WEB5, WEB64

compat-postgresql-libs

4-1PGDG

No

BSD

WEB5, WEB64

procmail

3.22-17.1

No

GPLv2

WEB5, WEB64

rsync

2.6.8-3.1

No

GPLv2

N/A

samba-client

3.0.33-3.29.el5_5.1

No

GPLv2

N/A

samba-common

3.0.33-3.29.el5_5.1

No

GPLv2

N/A

libsmbclient

3.0.33-3.29.el5_5.1

No

GPLv2

N/A

sendmail

8.13.8-8

No

Sendmail

N/A

shared-mime-info

0.19-5

No

GPLv2

N/A4

startup-notification

0.8-4.1

No

LGPLv2.0

N/A

sudo

1.7.2p1-9.el5_5

No

BSD

N/A

telnet

0.17-39

No

BSD

N/A

ttmkfdir

3.0.9-23

No

LGPLv2.0

N/A

unixODBC

2.2.11-7.1

No

LGPLv2.1

N/A

unzip

5.52-3

No

BSD

N/A

urw-fonts

2.3-6.1.1

No

GPLv2

N/A

words

3.0-9.1

No

Public Domain

N/A

xorg-x11-filesystem

7.1-2.fc6

No

MIT-X11

N/A

xorg-x11-font-utils

7.1-2

No

BSD

N/A

xorg-x11-xfs

1.0.2-4

No

MIT

N/A

zip

2.31-2

No

BSD-InfoZip

N/A

t1lib

5.1.0-1

No

LGPLv2.1

N/A

libXaw

1.0.2-8.1

No

MIT

N/A

libXmu

1.0.2-5

No

MIT

N/A

libedit

20090923-3.0_1

No

BSD

N/A

libtool-ltdl

1.5.22-7.el5_4

No

LGPLv2.1

N/A

freetds

0.64-11

No

LGPLv2.1

N/A