Free session3 initialization failed software for linux

sysinit is a system initialization and daemon management scheme for Linux (and possibly other Unix-like operating systems).

The system initialization portion has no external requirements except a working BASH shell. The daemon management portion requires a working BASH shell and either runit or daemontools. There are additional scripts that work with runit as process number one.

You may use it under the terms of the GNU General Public License.

PostScript::File is a Perl base class for creating Adobe PostScript files.

SYNOPSIS

use PostScript::File qw(check_tilde check_file
incpage_label incpage_roman);

Simplest

An hello world program:
use PostScript::File;

my $ps = new PostScript::File();

$ps->add_to_page( Letter,
height => 500,
width => 400,
bottom => 30,
top => 30,
left => 30,
right => 30,
clip_command => stroke,
clipping => 1,
eps => 1,
dir => ~/foo,
file => "bar",
landscape => 0,

headings => 1,
reencode => ISOLatin1Encoding,
font_suffix => -iso,

errors => 1,
errmsg => Failed:,
errfont => Helvetica,
errsize => 12,
errx => 72,
erry => 300,

debug => 2,
db_active => 1,
db_xgap => 120,
db_xtab => 8,
db_base => 300,
db_ytop => 500,
db_color => 1 0 0 setrgbcolor,
db_font => Times-Roman,
db_fontsize => 11,
db_bufsize => 256,
);

PerlActor is a simple automated executable acceptance test framework for Perl.

PerlActor is a simple automated executable acceptance test framework for Perl. It can be used by Extreme Programming (XP) teams to rapidly develop executable acceptance tests for their Perl code.

XP mandates that the Customer writes acceptance tests for the application under development. The acceptance tests, also known as customer tests, demonstrate that application features are complete and that they work as expected. Ideally, the tests should be directly executable and automated so that they can be run continuously, without manual effort.

PerlActor enables an XP Customer to write *executable* acceptance tests as plain text files, using a very simple syntax. Each test consists of a number of parameterized commands (one per line), which PerlActor uses to exercise the application. PerlActor parses the test, invokes the commands with any parameters, and reports the result. The developers provide glue code to implement the commands required by the tests.

PerlActor allows tests to be grouped into suites so that related tests can be run as a group. The Customer can also just place test scripts in a directory structure and have PerlActor find and execute them all.

The PerlActor approach to acceptance testing has a number of advantages:

1) As the application grows the team will gradually develop a comprehensive set of Commands for testing the application.
2) The Customer, independent of the development team, can write and execute new tests for the application at any time, using any of the existing Commands.
3) Existing tests may be changed by the Customer at any time, again without developer help.

EXAMPLE SCRIPT

The following sample test script is adapted from one of the example scripts contained in the examples/calculator directory of this distribution. It tests a toy calculator "application":

# Script to check addition
# 10 + 32 = 42

# Create a new calculator application
NewCalculator

# Ensure that the display reads 0, initially
CheckDisplayReads 0

# Press key 1, then key 0
PressKeys 1 0
CheckDisplayReads 10

PressKeys +
CheckDisplayReads 10

PressKeys 3 2
CheckDisplayReads 32

PressKeys =
CheckDisplayReads 42

The following is sample output from the included test runner:

Running Acceptance Tests at Sun Apr 10 17:59:11 GMT 2005
==========================================================
.....
0.545077 wallclock secs ( 0.42 usr + 0.11 sys = 0.53 CPU)
Run: 5, Passed: 5, Failed: 0, Aborted: 0.
and with test failure:
Running Acceptance Tests at Sun Apr 10 18:04:36 GMT 2005
==========================================================
.F...
1.24811 wallclock secs ( 0.47 usr + 0.07 sys = 0.54 CPU)
Run: 5, Passed: 4, Failed: 1, Aborted: 0.

!!!FAILED!!!

1) FAILED: Display is wrong: expected 41, got 42 in scripts/test_addition.pact
at CheckDisplayReads 41, line 37

Vonage::Click2Call is a Perl extension for using the Vonage Click2Call service.

SYNOPSIS

use Vonage::Click2Call;

my $vonage = Vonage::Click2Call->new(login => user,
password => pass,
no_https_check => 1, # wasteful after the first time. turn it off.
);
if (! $vonage) {
# no $vonage for errstr...
die "Failed during initilization : " . $Vonage::Click2Call::errstr;
}

# get my phone numbers
my @phoneNumbers = $vonage->fromNumbers();
if (! defined($phoneNumbers[0])) {
die "No phone numbers found : " . $vonage->errstr;
}
printf("I have %d numbers configured.",scalar(@phoneNumbers));

# call someone. dont forget the leading 1.
my $rc = $vonage->call($phoneNumbers[0],12125551234);
if (! $rc) {
die "Failed to place a call : " . $vonage->errstr;
}

Apache::AxKit::XSP::Language::SimpleTaglib is an alternate XSP taglib helper.

SYNOPSIS

package Your::XSP::Package;
use Apache::AxKit::Language::XSP::SimpleTaglib;

... more initialization stuff, start_document handler, utility functions, whatever
you like, but no parse_start/end handler needed - if in doubt, just leave empty ...

package Your::XSP::Package::Handlers;

sub some_tag : attrib(id) attribOrChild(some-param) node(result) keepWhitespace {
my ($e, $tag, %attr) = @_;
return do_something($attr_some_param,.$attr{id}.);;
}

This taglib helper allows you to easily write tag handlers with most of the common behaviours needed. It manages all Design Patterns from the XSP man page plus several other useful tag styles.

Measuring Buffer 20090628 provides you with a perfect and enhanced version of buffer which features display of throughput, network support, memory-mapped file I/O for huge buffers and multithreading. This will be your excellent choice.

Catalyst::Plugin::Authentication::Credential::BBAuth is a Yahoo! Browser-Based Authentication for Catalyst.

SYNOPSIS

use Catalyst qw(
Authentication
Authentication::Credential::BBAuth
Session
Session::Store::FastMmap
Session::State::Cookie
);

MyApp->config(
authentication => {
use_session => 1, # default 1. see C::P::Authentication
bbauth => {
appid => your appid,
secret => your secret,
},
},
);

sub default : Private {
my ( $self, $c ) = @_;
if ( $c->user_exists ) {
# $c->user setted
}
}

# redirect BBAuth login form
sub login : Local {
my ( $self, $c ) = @_;
$c->res->redirect( $c->authenticate_bbauth_url );
}

# login callback url
sub auth : Path(/auth) {
my ( $self, $c ) = @_;
if ( $c->authenticate_bbauth ) {
# login successful
$c->res->redirect( $c->uri_for(/) );
} else {
# login failed
}
}

This module provide authentication via Yahoo! Browser-Based Authentication, using its api.