Free resource standard metrics software for linux

Resource Management Game project is a Web-based resource management game.

Resource Management Game is a PHP framework for easily creating resource management and strategy games.

Two playable games are included.

The system uses sessions to store data and should work out of the box with little or no configuration.

Ch is an embeddable C/C++ interpreter for cross-platform scripting, shell programming, 2D/3D plotting, numerical computing, and embedded scripting. C/Ch/C++ allow users to use one language, anywhere and everywhere, for any programming tasks. Ch is the solution for:
- Embedded Scripting
- Enterprise
- Academic
- Plotting and Numerical Computing
C++ is C plus plus minus. Ch is C plus (Ch = C+). Ch is a C interpreter. Ch is C with classes and high-level extensions. Ch is a superset of C. Note that C++ is no longer a superset of C. For example, VLA and IEEE floating-point arithmetic in C are not supported in C++.
C is for low-level system programming and embedded systems; C++ for large-scale projects. Ch is optimal for platform-independent scripting in numerical computing and visualization, rapid application development, Web programming and plotting, embedded scripting, shell programming and integration with legacy systems.
Like C++, Ch is designed to be a superset of C, which means a C program can run in Ch without modification. Unlike C++ which is designed for serious professional programmers (elite), Ch is designed for both novice beginners with no computer experience (average Joe and John) as well as experienced programmers.

Resources is a Perl module to handle application defaults in Perl.

SYNOPSIS

use Resources;

$res = new Resources;
$res = new Resources "resfile";

Resources are a way to specify information of interest to program or packages.
Applications use resource files to specify and document the values of quantities or attributes of interest.

Resources can be loaded from or saved to resource files. Methods are provided to search, modify and create resources.

Packages use resources to hardwire in their code the default values for their attributes, along with documentation for the attibutes themselves.

Packages inherit resources when subclassed, and the resource names are updated dynamically to reflect a class hierarchy.

XML Schema Standard Type Library, in short XSSTL, is a collection of universally-useful data types defined in the W3C XML Schema language. The provided types describe concepts such as email address, IP address, phone number, country code, US states, etc.
To make all the types from XSSTL available in your schema simply add the following import directive:
< import namespace="http://www.codesynthesis.com/xmlns/xsstl"
schemaLocation="xsstl.xsd"/ >
And the following namespace-to-prefix mapping to your schema root:
xmlns:stl="http://www.codesynthesis.com/xmlns/xsstl"
Alternatively, you can import individual types:
< import namespace="http://www.codesynthesis.com/xmlns/xsstl"
schemaLocation="xsstl/email-address.xsd"/ >
< import namespace="http://www.codesynthesis.com/xmlns/xsstl"
schemaLocation="xsstl/phone-number.xsd"/ >
Enhancements:
- This initial version includes the following data types: EmailAddress, IPv4Address, Port, IPv4Endpoint, IPv4EndpointStruct, ISO3166CountyCode, Percentage, PhoneNumber, PhoneCountryCode, PhoneAreaCode, PhoneSubscriberNumber, PhoneExtensionNumber, PhoneNumberStruct, RFC822DateTime, USStateTerritoryCode, USStateCode, USTerritoryCode, USContinentalStateCode, and USContiguousStateCode.

1060 NetKernel is a resource oriented microkernel and application server that provides a coherent execution abstraction that radically reduces software complexity. Its self-consistent design is based on the convergence and unification of powerful fundamental concepts found in the World Wide Web and Unix.
Resource Oriented Microkernel
The heart of NetKernel is a high-performance, carefully designed, and tightly crafted microkernel. Services and resources within NetKernel are located by URI addresses, just as resources are located on the World Wide Web. NetKernel implements and extends REST 1 into a general-purpose processing abstraction and allows it to be applied to the finest granularity of software systems to achieve phenominal performance; just as the REST Web-architecture achieves global scaling and high performance.
Coherent Abstraction
NetKernel unifies code execution and resource identification into a single addressing and processing abstraction. With this, software development becomes a process of construction (coding services), composition (linking and issuing service and resource requests), and constraint (restricting data values and honoring boundaries).
The simplicity of URI identified resources means that the results of service calls can be cached just as other resources, resulting in self-optimizing software where computation cost is a guaranteed minima.
Reduce Software Complexity
The unification of resources and services with URI addressing radically reduces sofware complexity. Because resources are addressed by URI and each request is a Web-like REST request dispatched to the microkernel, binding between clients and services occurs dynamically for each request. This late binding and the indirection of logical URI addressing results in a loosely coupled system which may be easily adapted. In fact, NetKernel supports dynamic upgrading of software and can support multiple versions of the same components simultaneously.
Complexity brought about by system growth is also managed through the URI address space which may be remodelled and extended indefinitely. A complex aggregation of services may always be abstracted into one or more higher-level services surfaced through URI interfaces.
Main features:
Manage Complexity
- NetKernels unification of resource and service addressing through the active URI scheme combined with late binding and loose typing means that complex systems can be partitioned not just into smaller coorperating systems, you can now create micro-services that hide complexity.
- With NetKernel, design and build larger and more ambitious systems while maintaining control of complexity.
Process XML with ease!
- Processing XML is often just too difficult. But the potential of XML is communication with almost no limit. How to harness and leverage the potential of XML? NetKernel provides hundreds of XML technologies as simple services (no APIs). Simply compose XML services into powerful message processes...
Integrate diverse technologies, apply business logic
- NetKernels uniform URI addressing of resources and service allow you to encapsulate and hide the complexities of any technology, whether it is a Java API, legacy code, or remote corporate systems. Once encapsulated, develop new coordination logic in one of NetKernels scripting languages.
Transport technology independence
- Write a service or application and deploy it to service requests from multiple transports concurrently. NetKernel makes it easy to utilize SOAP 1.1, SOAP 1.2, HTTP, JMS, Email, and Cron.
Extreme performance from intra-application caching
- NetKernels fine-grained dependency cache transparently and opportunistically caches the results of all micro-service requests. NetKernel processes are self-optimizing with guaranteed minimal processing required for a given transaction.
Team Player
- NetKernel has several deployment options that allow it to play well with other technologies and systems. Deploy NetKernel as an advanced standalone application server, as an embedded "co-processor" within existing J2EE applications, as a JMS message processor, as a SOAP client or server, or as an embedded component within any application.
Enhancements:
- New features include support for Berkeley DBXML and PiNKY, a community developed module providing Yahoo! Pipes features.
- Updates include Groovy language support at release 1.0, Ruby (JRuby) support at 0.9.9, and XML library updates.
- There are also documentation updates and UI refinements.

GRIA (Grid Resources for Industrial Applications) is Grid middleware that enables use of the Grid in a secure, interoperable and flexible manner.
Security
GRIA uses off-the-shelf Web Services technology and Public Key Infrastructure (PKI) security.
Trust
GRIA supports well established B2B processes & trust models.
Ease of use
GRIA is designed to support leading-edge and legacy application codes, and client-side applications can be easily written using the GRIA API.
Quality of Service
GRIA resource models allow service levels to be matched to clients needs.
Support
GRIA is supported through an open source community and on a commercial basis.
Enhancements:
- This release provides significant new features and usability enhancements to both the management packages and the client.
- The core infrastructure stack has been further aligned with key Web Service security and policy specifications.
- New services include a Membership Service, Registry Service, and an improved SLA service.

Storage Resource Broker is client-server middleware that provides a uniform interface for connecting to heterogeneous data resources over a network and accessing replicated data sets.
SRB, in conjunction with the Metadata Catalog (MCAT), provides a way to access data sets and resources based on their attributes and/or logical names rather than their names or physical locations.
Starting with SRB 2.1.1 we now have an install script, install.pl, that can do a complete Postgres, MCAT and SRB installation. See README.MCAT.INSTALL. With SRB 3.0.0, this script can run on Solaris too, as well as the original Linux and Mac OS X.
The SEA authentication system is no longer recommended; for the secure authentication use either the ENCRYPT1 form of MDAS_AUTH authentication, or GSI. It should be noted that if the SEA authentication scheme is to be used and if the SEA library (libsea.a) does not already exist on your build platform, the SEA software that can be downloaded at the
URL must be built first.
1) Build configuration.
This version uses the configure script to configure the build. Most of the configurable parameters for building the SRB server and client can be configured using the "./configure" script. Run "./configure --help" for more information.
All configurable parameters for building the SRB server and the client library, including those set by the configure script, are defined in the mk/mk.config.in file. (The configure script automatically generates a third file, mk/mk.config, using mk/mk.config.in as a
template.)
Those parameters that cannot be modified via the configure script (because flags for those parameters have not yet been implemented) are set by directly editing the mk/mk.config.in file prior to running "./configure". Comments in the mk/mk.config.in file make it clear whether or not a particular parameter can be set through the configure
script, and if so, how to do so.
NOTE: The configure script does a number of self tests before the configuration is carried out. One of the test it does is the compiler test which it assumes "gcc" as the default compiler. If "gcc" is not installed or if the test of "gcc" failed (which happened on an AIX platform), the configure script should be re-run with the env variable CC set to cc or other compilers. This will override the default in the compiler test.
If the configure script still failed, do the following:
a) cd SRB2_0_0rel
b) ./config.rescue
c) edit the mk/mk.config file
2) Configure examples
a) Non-MCAT-enabled server and client, type in
configure
This will configure the mk.config file to build a non-MCAT enabled
server and client with the default settings.
b) Non-MCAT-enabled server and client with java enabled, type in
configure --enable-javagui=yes --enable-jdkhome=/usr/local/apps/jdk1.4.1
where /usr/local/apps/jdk1.4.1 is the directory where the JAVA JDK 1.4.1
is installed.
c) MCAT-enabled server with Oracle 8.1.5 MCAT, type in
configure --enable-oramcat --enable-oraver=815
--enable-orahome=/usr/local/apps/oracle/product/8.1.7
where /usr/local/apps/oracle/product/8.1.7 is the Oracle home
directory.
2) Parameters in the mk/mk.config file
The SRB architecture supports multiple SRB servers running on various hosts. Each SRB server may be built with different options, as set by the configure script and/or defined in the mk/mk.config.in file. For example, the SRB server on host A may include the driver for accessing HPSS and the SRB server on host B may include the driver for accessing the Lobj stored in DB2, etc.
The parameters are self-explanatory through the comments given in this file. Some of the more important parameters are discussed below:
installDir - The absolute path of the SRB install directory.
PORTNAME - The OS platform of this SRB port. Currently, the SRB software runs on 8 platforms. i.e., valid PORTNAMEs are :
PORTNAME_solaris, PORTNAME_sunos, PORTNAME_linux, PORTNAME_osx,
PORTNAME_aix, PORTNAME_alpha, PORTNAME_c90 and PORTNAME_sgi.
SRB_LARGEFILE64 - defines whether the 64 bit file size is supported by the underlining driver of this SRB server. Current, 64 bit file size is supported by the ORTNAME_solaris, PORTNAME_aix, PORTNAME_linux and PORTNAME_c90 platforms.
ORAMCAT - defines that this SRB server being built is MDAS enabled and the MCAT is stored in Oracle DBMS. Normally, only one SRB server is MDAS enabled.
DB2MCAT - defines that this SRB server being built is MDAS enabled and the MCAT is stored in Oracle DBMS. Normally, only one SRB server is MDAS enabled.
NOTE : Both ORAMCAT and DB2MCAT cannot be defined at the same time.
ADDR_64BIT - defines whether to compile for 64 bits address. This option has only been tested for the the Solaris and Linux platforms.
PARA_OPR - defines whether this SRB server support parallel operation API.
MDAS_AUTH - defines whether the plain text and encrypted password MDAS authorization scheme will be supported. If used, the user/passwd pair registered with the MDAS catalog will be used to authenticate a user. Comment it out if the SRB server does not support MDAS authorization.
NOTE : A server can be built to support either MDAS_AUTH (plain or encrypted (ENCRYPT1)) or GSI_AUTH, or both.
SEA_AUTH - defines whether SEA authorization scheme will be supported. The software can be configured to support both SEA_AUTH and MDAS_AUTH. (SEA is no longer recommended.)
LIB_SEA - Is needed only if SEA_AUTH is defined. LIB_SEA specifies where the SEA client library is located.
GSI_AUTH - defines whether the GSI authentication scheme is supported. This is set when --enable-gsi-auth is included on the configure line.
NOTE : A server can be built to support either MDAS_AUTH or GSI_AUTH,
or both.
LIB_GSI_AUTH - Set by configure when --enable-gsi-auth is included (i.e. GSI_AUTH is defined). LIB_GSI_AUTH specifies where the GSI client libraries are located. The optional configure --enable-globus-location=path can also be used specify the parent
location of the GSI libaries, and will cause LIB_GSI_AUTH to be adjusted.
JAVA_GUI and javaDir - JAVA_GUI defines whether the srbBrowser should be built. javaDir specifies the directory where the JDK software is installed. (e.g. /usr/local/apps/Java). See README.srbBrowser for more details.
3) "cd" to the main SRB directory and type in "gmake clean" and then "gmake" to make the SRB software. The Makefile contains various options to make and clean all or a subset of the build.
- gmake --- build all.
- gmake clean --- clean all.
- gmake srb --- build only the SRB server and client.
- gmake clean_srb --- clean only the SRB server and client.
- gmake util --- build only the utilities (S commands). See README.utilities for more details.
- gmake clean_util --- clean only the utilities.
- gmake browser - build only the java srbBrowser GUI. See README.srbBrowser for more details.
- gmake clean_browser - clean only the java srbBrowser.
4) (Optional) Type in "gmake install" to install the software in the $(installDir) directory. This procedure installs the following modules in the $(installDir) directory:
bin/runsrb - The script that starts the SRB
bin/srbMaster2_0_0 - The frontend server.
bin/srbServer - The backend server (forked by the srbMaster1_0 for each client connection).
bin/libSrbClient.a - The client library.
data/hostAuthConfig - The optional (needed only if HOST_BASED_AUTH in the mk.config file is set) host based authorization configuration file.
data/mcatHost - This file identifies the host on which the MCAT enabled SRB server is running.
data/hostConfig - This is the optional SRB host configuration file. It is only needed when when you want to add aliases to your local hostName.
data/hpssCosConfig - This is the optional HPSS Class of Services configuration file. It is only needed if HPSS in the mk.config file is set.
data/hpssNodceAuth - The file contains authentication info for non-dce HPSS. It is only needed if the HPSS and NO_DCE flags in the mk.config file are set.
data/MdasConfig - The MDAS configuration file.
data/metadata.fkrel - This file defines the foreign key relationship between the MDAS catalog tables and is used internally by the SRB for query generation. This file should not be changed between releases.
data/LobjConfig - The database configuration file for the DB Large Object driver. Basically, it contains the userID and password for accessing each database server.
Enhancements:
- Three vulnerabilities that allow SRB users to read/write non-Vault files that are readable/writable by the the srbadmin user were fixed.
- A bug that causes the GridFTP driver to use the wrong credential to connect to GridFtp server was fixed.
- A file descriptor lock bug was fixed.
- Uploading files larger than 2 gigabytes into GridFtp resources now works.
- Timeout bugs that could arise when sending large numbers of files were fixed.
- A core dump problem for HPSS type resources involving parallel I/O on Linux servers was fixed.
- A new option -o was added to show collection ownership in SgetColl.