Free rush hour 1 software for linux

Rush Hour Puzzle Solver project is a Rush Hour puzzle solver that illustrates the solution with PostScript.

Rush Hour Puzzle Solver is a small C++ program that reads a Rush Hour board from a text file and produces a nice PostScript file that shows the shortest solution.

vPrise Workgroup application is a distributed environment that helps bridging development teams. vPrise Workgroup, allows users to communicate with one another on a project basis over time sheets, expense reports, issues, file exchange, tasks, schedules and calendars.
The tool can be divided into three distinct groups, where a user might be limited to the confines of a single group or utilize all features in all groups. The three feature groups within vPrise Workgroup are:
- Employee data submissions - allows distributed employees to submit hour reports and expense sheets.
- Management view - allows managers within an approval chain to approve/reject employee submitted time sheets. Furthermore it allows the manager to sum up this information using reports.
- Collaboration tool set - allows employees of the company to communicate with other team members and customer teams. These features include file trading, a distributed calendar & issue tracking.

A lightweight IRC bot/dictionary, easy to set up, easy to localize.

Installation:

1) Edit the configuration file in config/config.tux.dist, change all values to suit your needs and then rename it to config.tux. Take your time to read through it, there are quite a few aspects you can alter

2) Create a new MySQL database with the name you set for db_base in the configuration file

3) Create a new MySQL user and grant it all privileges to the database you just created.

4) Create the tables required by the bot entering the following command
mysql -u db_user -p db_base < tux.sql

5) edit config/hosts.dist, add your hostmask to the file, save and then rename it to hosts

6) Now you should be all set up, go to the directory where the main program is and try to run it by entering

./tuxaator

With a little luck, you will be connected to server and choose the channel.

If you also want the bot to announce Freshmeat news and give information about kernel releases if asked, read on. If not, youre finished.



Setting up the external scripts

Tuxaator relies on external scripts to gather various information of interest from the Net. The scripts are not called from the bot, but are to be run separately, for example from the crontab.

Right now I have implemented 2 sample scripts:
kernel.sh - retrieves information about the latest kernels
fetchfm.sh - retrieves latest news from FreshMeat

Both scripts are located in the "scripts" directory of the installation and have to be configured separately, it is pretty straightforward though, just open them in your favourite text editor and follow the instructions.

Refer to "man 5 crontab" for information on how to setup the cronjobs.

My configuration looks like this:
1,31 * * * * /home/duke/tuxaator/scripts/fetchfm.sh > /dev/null
55 * * * * /home/duke/tuxaator/scripts/kernel.sh > /dev/null

This is, freshmeat news are retrieved 1 and 31 minutes after hour, and kernel news 55 minutes after hour. I found this configuration to be sufficient.

Ruby/Informix is a Ruby extension for connecting to IBM Informix Dynamic Server. It provides a convenient interface for querying an Informix database in Ruby programs.
Enhancements:
- This release fixes a bug in the code for interpreting DATETIME columns: time objects were being instantiated with incorrect values when the original ones had leading zeroes and the DATETIME column was defined with the HOUR TO SECOND qualifier.

StoCS is a service to control freespace on disk, mantain free space in a configurable level.

Works with three thresholds:

WARN: do a configurable action (dialog, message, alarm, ecc)
FDEL: deletion limit
LOWL: dimension to reach after deletion
If define must be LOWL < WARN < FDEL

Threshold unit can be:

Total number of file and/or subdiectory
Total dimension of controlle folder (Byte,Kbyte,Mbyte,ecc)
% of fre space on unit
Max age of files and/or subdirs (in this case LOWL is not used because all that exeeds is deleted)

Can work with a config file or wih command line parameters. Command line parameters overwrites config file values. Does not implements loop. Therefore you must use cron os similar.

Installation example

Copy stocs in /usr/local/bin
Copy stocs.conf in /usr/local/etc
Add to a cron.hourly (or a crontab):
/bin/su user -c "/usr/local/bin/stocs
-c /usr/local/stc/stocs.conf
&> /var/log/stocs.log"
In this case stocs runs every hour, using the configuration in stocs.conf, the output is written to log file /var/log/stocs.log

CryptoServer is OpenSource Server-side cryptography tool and run as daemon.

It is already tested in very busy environment and can support over one million transaction an hour.

CryptoServer accept the GPL License and can use it for any purpose as is.

iCal::Parser is a Perl module to parse iCalendar files into a data structure.

SYNOPSIS

use iCal::Parser

my $parser=iCal::Parser->new();
my $hash=$parser->parse($file);

$parser->parse($another_file);
my $combined=$parser->calendar;

my $combined=iCal::Parser->new->parse(@files);
my $combined=iCal::Parser->new->parse_files(@files);
my $combined=iCal::Parser->new->parse_strings(@strings);

This module processes iCalendar (vCalendar 2.0) files as specified in RFC 2445 into a data structure. It handles recurrences (RRULEs), exclusions (EXDATEs), event updates (events with a RECURRENCE-ID), and nested data structures (ATTENDEES and VALARMs). It currently ignores the VTIMEZONE, VJOURNAL and VFREEBUSY entry types.

The data structure returned is a hash like the following:

{
calendars=>[%cal, ...],
events=>{yyyy=>{mm=>{dd}=>{UID=>%event}}
todos=>[%todo, ...]
}

That is, it contains an array of calendar hashes, a hash of events key by year=>month=>day=>eventUID, and an array of todos.

Calendars, events and todos are "rolled up" version os the hashes returned from Text::vFile::asData, with dates replaced by DateTime objects.

During parsing, events in the input calendar are expanded out into multiple events, one per day covered by the event, as follows:
If the event is a one day "all day" event (in ical, the event is 24hrs long, starts at midnight on the day and ends a midnight of the next day), it contains no hour field and the allday field is set to 1.

If the event is a recurrence (RRULE), one event per day is created as per the RRULE specification.

If the event spans more than one day (the start and end dates are on different days, but does not contain an RRULE), it is expanded into multiple events, the first events end time is set to midnight, subsequent events are set to start at midnight and end at midnight the following day (same as an "allday" event, but the allday field is not set), and the last days event is set to run from midnight to the end time of the original multi-day event.

If the event is an update (it contains a RECURRENCE-ID), the original event is updated. If the referenced event does not exist (e.g., it was deleted after the update), then the event is added as a new event.
An example of each hash is below.

Podracer is a podcast downloader. It takes a file with the URLs to all your podcast rss feeds and goes and gets the mp3s and stores them in a specified location. Podracer is a Bourne Shell script with an internal BitTorrent downloader written in Python.
Main features:
- Catchup feature updates the log without downloading all podcasts
- Run as a cron job to automatically receive podcasts
- Properly fails (with no error message for the sake of cron) if already running
- Download podcast enclosures of any file format
- Support for BitTorrent downloading and seeding of podcasts
- Configurable seed time management - seed torrents for an hour or a day
- Background torrent seeding continues after program ends and stops automatically
- System-wide and user-specific configuration
- User-specific subscription file and podcast download directories
- Commentable subscription file - go ahead and mark it up
- Fully configurable placement of files and directories
- Support for dynamic creation of download directories, i.e. based on date/time
- Appears in podcasters logs as a podcast receiver
- Automatic creation of m3u playlists
- User may request that m3u not be created
- Automatic removal of empty download directories
- Your suggestions...