resources connection
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 2182
Resources 1.04
Resources is a Perl module to handle application defaults in Perl. more>>
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.
<<lessSYNOPSIS
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.
Download (0.018MB)
Added: 2007-05-10 License: Perl Artistic License Price:
899 downloads
Jabber::Connection 0.03
Jabber::Connection is a simple Perl module with connectivity functions for Jabber. more>>
SYNOPSIS
# client connection:
my $c = new Jabber::Connection(
server => jabber.org,
log => 1,
);
# component connection:
# my $c = new Jabber::Connection(
# server => localhost:5700,
# localname => comp.localhost,
# ns => jabber:component:accept,
# log => 1,
# debug => 1,
# );
die "oops: ".$c->lastError unless $c->connect();
$c->register_beat(10, &every_10_seconds);
$c->register_handler(presence,&presence);
$c->register_handler(iq,&handle_iq_conference);
$c->register_handler(iq,&handle_iq_browse);
$c->auth(qmacro,password,myresource); # client auth
# $c->auth(secret); # component auth
$c->send( );
$c->start;
DESCRIPTION ^
The Jabber::Connection package provides basic functions for connecting clients and components to a Jabber server.
Download (0.012MB)
Added: 2007-03-21 License: Perl Artistic License Price:
952 downloads
Gnome Remote Connection Manager 0.1.5
Gnome Remote Connection Manager is a gnome application that stores information about remote connections. more>>
Gnome Remote Connection Manager is a gnome application that stores information
about remote connections.
It gives you a GUI program to launch applications like telnet, shh, or rdesktop. It is highly configurable as to what type of applications it launches, so you are not limited to the three listed, for example I never thought of using it for ftp, but it would be easy to setup.
GRCM uses gconf to store information about connections.
Enhancements:
- Added some missing icons.
- Fixed a callback in the Connections Dialog that made the default arguments from the connection appear when selected.
<<lessabout remote connections.
It gives you a GUI program to launch applications like telnet, shh, or rdesktop. It is highly configurable as to what type of applications it launches, so you are not limited to the three listed, for example I never thought of using it for ftp, but it would be easy to setup.
GRCM uses gconf to store information about connections.
Enhancements:
- Added some missing icons.
- Fixed a callback in the Connections Dialog that made the default arguments from the connection appear when selected.
Download (0.17MB)
Added: 2005-07-28 License: GPL (GNU General Public License) Price:
1553 downloads
Grid Resources for Industrial Applications 5.1
GRIA is Grid middleware that enables use of the Grid in a secure, interoperable and flexible manner. more>>
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.
<<lessSecurity
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.
Download (MB)
Added: 2007-05-24 License: GPL (GNU General Public License) Price:
886 downloads
QoS Connection Tuning HOWTO 0.61
QoS Connection Tuning HOWTO is a document which explains how to tune network connection performance. more>>
QoS Connection Tuning HOWTO is a document which explains how to tune network connection performance.
This enables you to get the maximum benefit out of your connection without lag and loss.
<<lessThis enables you to get the maximum benefit out of your connection without lag and loss.
Download (MB)
Added: 2006-10-10 License: (FDL) GNU Free Documentation License Price:
1115 downloads
Net::FreeDB2::Connection 0.8.2.6
Net::FreeDB2::Connection is a FreeDB/CDDB abstract connection class. more>>
Net::FreeDB2::Connection is a FreeDB/CDDB abstract connection class.
Net::FreeDB2::Connection is an abstract class to represent connections to FreeDB/CDDB servers. After a successfull connection, FreeDB/CDDB queries, reads etc can be made to obtain/provide information from/to FreeDB/CDDB databases.
CONSTRUCTOR
new (OPT_HASH_REF)
Creates a new Net::FreeDB2::Connection object. By default connect () is called to initiate the connection but see option no_connect. See the implementation for complements/restrictions.
Options for OPT_HASH_REF may include:
client_name
Mandatory option to name the connecting client software.
client_version
Mandatory option with the client software version string.
client_host
The hostname of the client. Defaults to &Sys::Hostname::hostname ().
client_user
The user of the client. Defaults to scalar (getpwuid ($>));
freedb_host
The FreeDB/CDDB host. Defaults to freedb.freedb.org.
freedb_port
The port on the FreeDB/CDDB host.
proxy_host
Proxy host.
proxy_port
Port on the proxy host. Defaults to 8080.
proxy_user
Proxy user name to use.
proxy_passwd
Proxy password to use.
no_connect
Do not call connect () during instanciation.
<<lessNet::FreeDB2::Connection is an abstract class to represent connections to FreeDB/CDDB servers. After a successfull connection, FreeDB/CDDB queries, reads etc can be made to obtain/provide information from/to FreeDB/CDDB databases.
CONSTRUCTOR
new (OPT_HASH_REF)
Creates a new Net::FreeDB2::Connection object. By default connect () is called to initiate the connection but see option no_connect. See the implementation for complements/restrictions.
Options for OPT_HASH_REF may include:
client_name
Mandatory option to name the connecting client software.
client_version
Mandatory option with the client software version string.
client_host
The hostname of the client. Defaults to &Sys::Hostname::hostname ().
client_user
The user of the client. Defaults to scalar (getpwuid ($>));
freedb_host
The FreeDB/CDDB host. Defaults to freedb.freedb.org.
freedb_port
The port on the FreeDB/CDDB host.
proxy_host
Proxy host.
proxy_port
Port on the proxy host. Defaults to 8080.
proxy_user
Proxy user name to use.
proxy_passwd
Proxy password to use.
no_connect
Do not call connect () during instanciation.
Download (0.030MB)
Added: 2007-03-05 License: Perl Artistic License Price:
965 downloads
Resource Management Game 0.12
Resource Management Game project is a Web-based resource management game. more>>
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.
<<lessResource 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.
Download (0.081MB)
Added: 2007-01-10 License: GPL (GNU General Public License) Price:
1022 downloads
Resource::Loader 0.03
Resource::Loader is a Perl module to load different resources depending. more>>
Resource::Loader is a Perl module to load different resources depending.
SYNOPSIS
use Resource::Loader;
$loader = Resource::Loader->new(
testing => 0,
verbose => 0,
cont => 0,
resources =>
[
{ name => never,
when => sub { 0 },
what => sub { die "this will never be loaded" },
},
{ name => sometimes 50%,
when => sub { int rand 2 > 0 },
what => sub { "sometimes was loaded. args: [@_]" },
whatargs => [ qw/foo bar baz/ ],
},
{ name => sometimes 66%,
when => sub { int rand @_ },
whenargs => [ 0, 1, 2 ],
what => sub { "sometimes was loaded. args: [@_]" },
whatargs => [ qw/foo bar baz/ ],
},
{ name => always,
when => sub { 1 },
what => sub { "always was loaded" },
},
],
);
$loaded = $loader->load;
$status = $loader->status;
Resource::Loader is simple at its core: You give it a list of resources. Each resource knows when it should be triggered and if its triggered, will run its code segment.
Both the when and the what are coderefs, so you can be as devious as you want in determining when a resource will be loaded and what, exactly, it does.
I originally wrote this to solve a simple problem but realized that the class is probably applicable to a whole slew of problems. I look forward to hearing to what devious ends you push this module. Really, send me an email - I love hearing about people using my toys.
<<lessSYNOPSIS
use Resource::Loader;
$loader = Resource::Loader->new(
testing => 0,
verbose => 0,
cont => 0,
resources =>
[
{ name => never,
when => sub { 0 },
what => sub { die "this will never be loaded" },
},
{ name => sometimes 50%,
when => sub { int rand 2 > 0 },
what => sub { "sometimes was loaded. args: [@_]" },
whatargs => [ qw/foo bar baz/ ],
},
{ name => sometimes 66%,
when => sub { int rand @_ },
whenargs => [ 0, 1, 2 ],
what => sub { "sometimes was loaded. args: [@_]" },
whatargs => [ qw/foo bar baz/ ],
},
{ name => always,
when => sub { 1 },
what => sub { "always was loaded" },
},
],
);
$loaded = $loader->load;
$status = $loader->status;
Resource::Loader is simple at its core: You give it a list of resources. Each resource knows when it should be triggered and if its triggered, will run its code segment.
Both the when and the what are coderefs, so you can be as devious as you want in determining when a resource will be loaded and what, exactly, it does.
I originally wrote this to solve a simple problem but realized that the class is probably applicable to a whole slew of problems. I look forward to hearing to what devious ends you push this module. Really, send me an email - I love hearing about people using my toys.
Download (0.008MB)
Added: 2007-03-05 License: Perl Artistic License Price:
968 downloads
Jack audio connection kit 0.103.0
JACK is a low-latency audio server, written for POSIX conformant operating systems such as GNU/Linux and Apples OS X. more>>
JACK is a low-latency audio server, written for POSIX conformant operating systems such as GNU/Linux and Apples OS X.
Jack audio connection kit can connect a number of different applications to an audio device, as well as allowing them to share audio between themselves. Its clients can run in their own processes (ie. as normal applications), or can they can run within the JACK server (ie. as a "plugin").
JACK was designed from the ground up for professional audio work, and its design focuses on two key areas: synchronous execution of all clients, and low latency operation.
<<lessJack audio connection kit can connect a number of different applications to an audio device, as well as allowing them to share audio between themselves. Its clients can run in their own processes (ie. as normal applications), or can they can run within the JACK server (ie. as a "plugin").
JACK was designed from the ground up for professional audio work, and its design focuses on two key areas: synchronous execution of all clients, and low latency operation.
Download (0.66MB)
Added: 2007-03-19 License: GPL (GNU General Public License) Price:
951 downloads
Net::Connection::Sniffer 0.13
Net::Connection::Sniffer can gather stats on network connections. more>>
Net::Connection::Sniffer can gather stats on network connections.
SYNOPSIS
use Net::Connection::Sniffer;
gather($config)
__top
Net::Connection::Sniffer is a perl module to gather connection statistics by listening to ethernet traffic. Traffic is filtered using standard BPF notation as described in the tcpdump documentation and implemented using the standard pcap library to sniff packets on host network interfaces.
<<lessSYNOPSIS
use Net::Connection::Sniffer;
gather($config)
__top
Net::Connection::Sniffer is a perl module to gather connection statistics by listening to ethernet traffic. Traffic is filtered using standard BPF notation as described in the tcpdump documentation and implemented using the standard pcap library to sniff packets on host network interfaces.
Download (0.042MB)
Added: 2006-07-27 License: Perl Artistic License Price:
1194 downloads
Storage Resource Broker 3.4.2
Storage Resource Broker is a network data storage middleware. more>>
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.
<<lessSRB, 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.
Download (16.5MB)
Added: 2006-07-07 License: Free For Educational Use Price:
1207 downloads
Connection Manager 1.0rc1
Connection Manager allows you to pre-configure all this, and use a single consistant interface. more>>
Connection Manager allows you to pre-configure all this, and use a single consistant interface to get connected to all of these various systems.
Do you have to log in to a lot of different systems? If you do, odds are that you have to use a variety of methods. You probably have some systems that require ssh and others that only support rdesktop. For some you may have to use vnc. Some may only support telnet. Connection Manager allows you to pre-configure all this, and use a single consistant interface to get connected to all of these various systems.
To install from the source distibution type (you probably will have to be root):
make install
To make rpms for rpm-based ditros type:
make rpm
Main features:
- Command Line Interface - Connection Manager will have a command line interface that allows for easy initiation of any connection. Some users, especially system administrators, will prefer this method of interaction
- Qt/KDE interface - Connection Manager will have a full featured graphical interface based on the Qt and KDE widgets. This interface will allow a user to manage their own connections, as well as maintain all of the various configuration files. You shouldnt have to use a text editor to edit configuration files unless you really want to
- Documentation - Connection Manager will be completely documented, including man pages, a user reference guide, and an administrator reference guide.
- Packaging - every effort will be made to make Connection Manager easy to install. Packages will be provided for a variety of platforms.
- Internationalization - Connection Manager will be designed and built so that it will be easy to add support for different languages.
<<lessDo you have to log in to a lot of different systems? If you do, odds are that you have to use a variety of methods. You probably have some systems that require ssh and others that only support rdesktop. For some you may have to use vnc. Some may only support telnet. Connection Manager allows you to pre-configure all this, and use a single consistant interface to get connected to all of these various systems.
To install from the source distibution type (you probably will have to be root):
make install
To make rpms for rpm-based ditros type:
make rpm
Main features:
- Command Line Interface - Connection Manager will have a command line interface that allows for easy initiation of any connection. Some users, especially system administrators, will prefer this method of interaction
- Qt/KDE interface - Connection Manager will have a full featured graphical interface based on the Qt and KDE widgets. This interface will allow a user to manage their own connections, as well as maintain all of the various configuration files. You shouldnt have to use a text editor to edit configuration files unless you really want to
- Documentation - Connection Manager will be completely documented, including man pages, a user reference guide, and an administrator reference guide.
- Packaging - every effort will be made to make Connection Manager easy to install. Packages will be provided for a variety of platforms.
- Internationalization - Connection Manager will be designed and built so that it will be easy to add support for different languages.
Download (0.031MB)
Added: 2006-07-01 License: GPL (GNU General Public License) Price:
1222 downloads
XML::DB::Resource
XML::DB::Resource is a Wrapper class for documents or document fragments. more>>
XML::DB::Resource is a Wrapper class for documents or document fragments.
SYNOPSIS
$resource = $collection->getResource($id);
$id = $resource->getId();
$xml = $resource->getContent();
$resource->setContent($xml);
$collection->storeResource($resource);
$parentColl = $resource->getParentCollection();
This is an abstract class implementing the Service interface Database from the XML:DB base specification. It should only be used indirectly, as superclass for a specific Resource type. The only current example is XMLResource.
<<lessSYNOPSIS
$resource = $collection->getResource($id);
$id = $resource->getId();
$xml = $resource->getContent();
$resource->setContent($xml);
$collection->storeResource($resource);
$parentColl = $resource->getParentCollection();
This is an abstract class implementing the Service interface Database from the XML:DB base specification. It should only be used indirectly, as superclass for a specific Resource type. The only current example is XMLResource.
Download (0.004MB)
Added: 2006-10-25 License: Perl Artistic License Price:
1094 downloads
JSecureTunneling 0.2.3
JSecureTunneling provides a Java SSH client for tunnels management. more>>
JSecureTunneling provides a Java SSH client for tunnels management.
SecureTunneling is a Java SSH client that is entirely oriented toward the management of SSH tunnels, offering the ability to establish secure and permanent tunnels to a remote SSH server transparently, just like a simple network connection.
The key features are: auto-reconnection, connection monitoring, connection triggers, tunneling changes on-the-fly, and profile management.
<<lessSecureTunneling is a Java SSH client that is entirely oriented toward the management of SSH tunnels, offering the ability to establish secure and permanent tunnels to a remote SSH server transparently, just like a simple network connection.
The key features are: auto-reconnection, connection monitoring, connection triggers, tunneling changes on-the-fly, and profile management.
Download (MB)
Added: 2007-03-02 License: GPL (GNU General Public License) Price:
966 downloads
RISE Project 0.1.0
RISE Projects goal is to produce software to efficiently manage and publish academic catalog information including programs. more>>
RISE Projects goal is to produce software to efficiently manage and publish academic catalog information including programs, courses, and schedules.
RISE means Resources and Information for Success in Education.
<<lessRISE means Resources and Information for Success in Education.
Download (0.065MB)
Added: 2006-08-17 License: BSD License Price:
1163 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 resources connection 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
