Free barracuda pool cleaners software for linux

Thread::Pool contains group of threads for performing similar jobs.

SYNOPSIS

use Thread::Pool;
$pool = Thread::Pool->new(
{
optimize => cpu, # default: memory

pre => sub {shift; print "starting worker with @_n",
do => sub {shift; print "doing job for @_n"; reverse @_},
post => sub {shift; print "stopping worker with @_n",

stream => sub {shift; print "streamline with @_n",

monitor => sub { print "monitor with @_n",
pre_post_monitor_only => 0, # default: 0 = also for "do"

checkpoint => sub { print "checkpointingn" },
frequency => 1000,

autoshutdown => 1, # default: 1 = yes

workers => 10, # default: 1
maxjobs => 50, # default: 5 * workers
minjobs => 5, # default: maxjobs / 2
},
qw(a b c) # parameters to "pre" and "post" routine
);

$pool->job( qw(d e f) ); # not interested in result

$jobid = $pool->job( qw(g h i) );
@result = $pool->result( $jobid ); # wait for result to be ready

$jobid = $pool->job( qw(j k l) );
@result = $pool->result_dontwait( $jobid ); # do _not_ wait for result

@result = $pool->waitfor( qw(m n o) ); # submit and wait for result

$pool->add; # add worker(s)
$pool->remove; # remove worker(s)
$pool->workers( 10 ); # adapt number of workers
$pool->join; # wait for all removed worker threads to finish

$workers = $pool->workers;
$todo = $pool->todo;
$removed = $pool->removed;

$pool->maxjobs( 100 ); # adapt or (de-)activate job throttling
$pool->minjobs( 10 );

$pool->autoshutdown( 1 ); # shutdown when object is destroyed
$pool->shutdown; # wait until all jobs done
$pool->abort; # finish current job and remove all workers

$done = $pool->done; # simple thread-use statistics
$notused = $pool->notused;

Thread::Pool->remove_me; # inside "do" only

Tournament Pool and Bracket Tracker is a Java Servlet based generic game tournament pool bracket tracking application suitable especially for the NCAA basketball championship tournament.
Features include bracket entering, multiple scoring systems, multiple users, groups, pools, etc.
Tournament Pool and Bracket Tracker contains everything you need to run a tournament pool.
It supports small groups or organizations who wish to provide an NCAA basketball tournament pool without a lot of administrative work in registering users or in calculating up-to-date results and possibilities.
Though it was built with the NCAA "March Madness" tournaments in mind, it should be able to handle other sport tournament pools that use straight forward brackets.
As an administrator, you will first log into the system like any other user. Any user can create a group and aministrate their own pool. A group is a set of players that play together in any number of pools.
Pool adminstrators can choose from many different scoring systems. Scoring systems can be set up dynamically in the database. When you set up a group, you have a choice. Either you can tell the users about the pool, and have them register, then notify you. You would then add the users to the group manually. This keeps membership totally within your control.
However, you can also create an invitation code. Youll then have an link to the system with that invitation code embedded. You can send this link to your users. When they click the link and login (with a possible detour through registration), they will be automatically added to your group.
They can then create their bracket and add it to a pool without your direct involvement. You do risk that the email gets circulated to others and people you dont intend to enter your group do.
Players can create as many brackets as they like, name them, leave them unfinished, come back to them later, etc. Players can add a bracket to a pool once the bracket is finished either from the bracket interface page or from the pool interface page.
Once a tournament is underway, users can keep track of their progress as the administrator for a tournament updates the results of games. Tournaments results are updated by the administrator with the same interface players use to enter their brackets.
Players are prevented from editing their brackets once it has been added to a pool that has a tournament underway. Tournament administrators can delegate the duty of keeping game results up to date to others if they arent going to be around for some of the games via a simple interface.
This allows players to come into the system regularly during the tournament and check their results and the standings much quicker than your typical spreadsheet based systems. If something is updated wrong, the players will keep you honest. The results show current, remaining, and maximum available points.
Any user can inspect the other players brackets in the pool. The brackets are presented with good picks in the green and bad picks in the red.
Version restrictions:
- Right now, all of the bracket, tournament, and teams setup is done via SQL scripts. I typically am working on the scripts the night they are announced. The priority list for the user interface work so far has been first to make the player experience nice, second to make the in-tournament administration nice, and only third to make the tournament setup nice. Hopefully by the time March 2006 rolls around this third area will be improved.
- At this point the bracket system wont handle highest seed meets lowest seed type of brackets. Unfortunately, this rules out using this system for the NFL Playoffs for the time being. Ive been working on this, but it is hard nut to crack.
Installation:
- Install MySQL and Tomcat
- Put the tournament.war file in the tomcat webapps folder.
- To get the database ready, run the following commands from the mysql.exe tool in the following order:
. [path]configdb.sql
. [path]configncaa.sql
. [path]configncaa-teams.sql
. [path]configncaa-2004.sql (optional)
. [path]configacc.sql (optional)
. [path]configacc-2005.sql (optional)
. [path]configncaa-2005.sql
You need to grant privileges in mysql as well:
GRANT ALL PRIViLEGES ON *.* TO testuser@localhost
IDENTIFIED BY testpw WITH GRANT OPTION;
Make some tweaks to the [tomcat home]/conf/web.xml file. Uncomment the following:
< !-- The invoker servlet -->
< servlet>
< servlet-name>invoker
< servlet-class>
org.apache.catalina.servlets.InvokerServlet
< /servlet-class>
< init-param>
< param-name>debug
< param-value>0
< /init-param>
< load-on-startup>2
< /servlet>
and
< !-- The mapping for the invoker servlet -->
< servlet-mapping>
< servlet-name>invoker
< url-pattern>/servlet/*
< /servlet-mapping>
This enables the autoinvoker servlet, which maps from URLs to class names which happen to be J2EE servlet classes. Some people consider this a security risk, which is why it is disabled by default. Ive never had an issue so long as I know all of the servlet classes I have in the system. This can be changed. If you consider it an issue, let me know via a feature request.
- Start MySQL and Tomcat
- Go to http://localhost:8080/tournament/
Enhancements:
- This release adds many new options for the tournament pool administrator.
- You can do tie breakers, not show the players brackets to each other until the tournament starts, limit the number of brackets per player, and run a pool starting later in a tournament, such as starting at the Sweet 16.
- There is also a new interface for setting the start date and time of the tournament, sorting enhancements, the ability to edit pool settings, ranking the brackets of a running pool, and players may reset their passwords.

Fast Data Transfer is an application for efficient data transfers that is capable of reading and writing at disk speed over wide area networks (with standard TCP).
It can be used to stream a large set of files across the network, so a large dataset composed of thousands of files can be sent or received at full speed, without the network transfer restarting between files.
The project is written in Java, runs an all major platforms, and is easy to use.
Main features:
- Streams a dataset (list of files) continuously, using a managed pool of buffers through one or more TCP sockets.
- Uses independent threads to read and write on each physical device
- Transfers data in parallel on multiple TCP streams, when necessary
- Uses appropriate-sized buffers for disk I/O and for the network
- Restores the files from buffers asynchronously
- Resumes a file transfer session without loss, when needed

Sharedance is a high-performance server that centralize ephemeral key/data pairs on remote hosts, without the overhead and the complexity of an SQL database.
Sharedance project was mainly designed to share caches and sessions between a pool of web servers. Access to a sharedance server is trivial through a simple PHP API and it is compatible with the expectations of PHP 4 and PHP 5 session handlers.
Sharedance is heavily used on Skyblog.
Enhancements:
- The Nagle algorithm has been disabled.
- Log messages are now in local time.
- Some minor bugs have been fixed.

Loki Render software is a queue manager. It serves Blender render jobs or your own scripts to a pool of clients.

This is commonly called "distributed network rendering" or a "render farm". Loki can also boot clients via PXE, making for a quick and scalable pool.

FooBillard is a free OpenGL-billard game for Linux with realistic physics, AI-player and many gametypes like pool carambol or snooker. Why foo? Well, actually I had this logo (F.B.-Florian Berger) and then foo sounds a bit like pool (Somehow I wasnt quite attracted by the name FoolBillard) The main physics is quite mature but not yet perfect. If you are a billard-pro and youre missing some physics, please tell me. Cause Ive implemented it like I think it should work, which might differ from reality.
There are two supported implementations concerning the interface. A GLUT and an SDL implementation. So you need to have either GLUT or SDL installed on your system Furthermore libpng has to be installed for loading the textures and freetype2 is required for font rendering.
Main features:
- wood paneled table with gold covers and gold diamonds
- reflections on balls
- shadow pixmaps
- detail switching of balls according to distance
- zoom in/out - hold right mousebutton
- FOV +/- - hold right mousebutton + CTRL
- rotate - hold left mousebutton
- animated queue
- 8ball, 9ball, snooker, carambol
- simple AI-Player
- strength adjustment
- eccentic hit adjustment (button2-Shift)
- red/green 3D stereo view !!!
- sound
- network play
- free view mode

Penny Pool is a small utility to ease the pooling of expenses.
It facilitates the administration of many (small) shared expenses, which typically add up to significant amounts. It uses PHP/MySQL/Apache, and has an emphasis on easy installation.
A well-known problem in groups of people is how to distribute costs of collective payments. What usually happens is that one person pays and expects the rest of the group to then pay their respective shares to him / her. This is not a problem for a single incident, but when multiple events occur, with different persons paying, it would clearly be better to pool these events.
Payments can then be set up within the group, such that the number of money transfers is minimized.
PennyPool helps in administering these kinds of expenses in the form of a simple web application. First of all, the mere fact that expenses can be entered in a central location (to which everyone has access) makes it clear to everyone who should pay what. Furthermore, it is possible to group these expenses in settlements, which can be used as a starting point for actual payments among the members of the group.
These payments can also be entered and attached to the settlement. In this way, the progress of the settlement can be seen and it is obvious how much should still be paid.
The database only stores information that was entered directly. All presented data (e.g. balance) is calculated in real-time.
Precision is therefore limited by MySQL and/or PHP, only two decimal places are shown for readability. (this also means that the cents/pennies dont always add up, in which case a "miereneuker" should use the rounded cumulative result. As opposed to harassing me...)
Enhancements:
- It is now possible to bill participants multiple times. This makes it easy to use PennyPool even when some participants to an event are not registered users.